| Release Billing Documents to Accounting
Is there a way to run VFK3 in background? When I execute the transaction the "execute in background" option is greyed-out. If you would like to run it in background,you have to use the program RVFAKSPE instead of SDBLBDDL. There had been a change of the program used in transaction VFX3 for release 4.5B and afterwards. You can see this in the System -> Status screen. The program used in releases up to 4.5B is RVFAKSPE, in releases after 4.6A it is SDBLBDDL. Report SDBLBDDL can't be used for processing in the background, it is not designed to run as a batch job. You can still process the release to accounting in background processing by creating background jobs for program RVFAKSPE, which is still available. Is there any T.code for finding the billing document was not released to accounting? Please use Tcode VFX3 You can find the same against the following: Sales organization*
While entering the billing document in vf01, you got
the following information, how to make it?
Go to release for accounting. However if it does not create automatically there will be a problem posting to Finance. I would then suggest that you use t code VFX3 to release the billing document to Finance. There is a log in both VF02 and VFX3 that will show what the error is. First thing to do is re-checking the config for revenue account determination. This is known in the IMG as "revenue account determination", but it covers a lot more than that (discounts, taxes etc). This is what determines how the financial impact of your SD Billing document is posted into the FI General Ledger. The integration is controlled both in SD and in FI. In SD there is a awesome area of configuration called the pricing procedures. The pricing procedure determines the final price quoted to the customer for a particular product. This could be a complicated calculation taking into account the base price, any special prices or discounts that may apply to that scenario, taxes, freight charges etc. These prices or charges are called 'condition types'. This condition technique is used in a number of areas of SAP. For now all we need to know is that each condition type is assigned to an account key (or in the case of rebates two account keys). You can assign multiple condition types to the same account key. There are a number of account keys that are pre-defined in the system. For example: - ERF freight revenues
Now we start getting to the integration by mapping the account keys to GL accounts. But it is not as simple as that. It can be as flexible (ie: as complex) as you want. Start off with the most simple approach. Generally if one is using a good sales / revenue reporting tool (eg: CO-PA) then one does not need a lot of flexibility and variety in the GL accounts that are posted to. The level of detail that you need in GL should be determined by your financial statement reporting requirements - you may end up with only one Revenue account - it is a good bet! So, taking the simple approach we would ignore most of the configuration possibilities : procedures, access sequences, condition tables etc (Yes it is that 'condition technique' kicking in again. Once you have worked through it once in one area and encounter it in another then hopefully you will be comfortable in knowing that most of the standard configuration can be left as is. ) We have to decide which access sequences we want to use (Five access sequences are defined in the standard SAP R/3 System). To keep it simple, let us assume we just use one - for example: the access sequence "chart of accounts/sales org./account keys". The chart of accounts part is standard in all account determinations, so let us look at the rest. This access sequence allows us to specify different GL accounts for different Sales Organisations. Also check the customer master record for account assignment group.
SAP SD Books :-
Goto:
Goto:
Back to :-
Return to :-
(c) www.gotothings.com All material on this site is Copyright.
|