Posts filed under 'FUNCTIONAL'

Error while AUC settlement

While my client settle AUC into new fiscal year which acquisition on old fiscal year, error “Settlement of Old Asset Data to Receiver Type G/L Not Allowed” happen. Full message from SAP you can see like below:

Message from SAP :

Settlement of Old Asset Data to Receiver Type G/L Not Allowed
Message no. AW607Diagnosis
You tried to settle values from the previous year to a receiver other than
an asset. This procedure is not supported by the system.

Procedure
Check your distribution rules and change the receiver.

 

I have been check the distribution rule of AUC, 80 % settle into fix asset and 20% settle into G/L expense. This problem happen only if the AUC settlement is running on different fiscal year (acquisition on old fiscal year, and settlement on new fiscal year). Based on the message I conscious that SAP configuration does not allow for this distribution in different fiscal year.  

I’ve been think for an hours for this problem and finally I got idea for the solution. First, I change the distribution rule from fix asset and expense into AUC. And then run the settlement, after that the distribution rule change into fix asset and expense and run again the settlement…. Thanks God its working.

4 comments April 28, 2008

Improving WIP Calculation

            My client has been decided to change the production strategy from discrete manufacturing to repetitive manufacturing. Discrete manufacturing produce production order,  and the problem is many production order pending (status is not closed).

            As a result of the above condition, WIP calculation  performance is getting down from one hours become a day and finally WIP calculation is not run properly.

I found some note from SAP library, give me some tips how to improve WIP calculation performance. The note said that you can significantly improve the performance of WIP calculation by setting the status DLFL (Deletion flag)  for the following orders:

·         The order is delivered or technically completed

·         Variances have been calculated for the order

·         You do not anticipate any further follow-up costs for the order

Practically I do the following action above and finally the performance of WIP – calculation was improved significantly.

 

Appendix :

WIP : Work in process

1 comment September 5, 2007

SAP Error “Complete allocation structure P1” during wbs settlement using t-code CJ88

Here I share my experience in my client about error during settlement WBS using t-code CJ88. This error appear when finance staff trying to settle their WBS (budget).The root cause is there transaction with in cost element use on goods issue transaction but the cost element is not member of allocation structure.

The message from SAP look like below :

Complete allocation structure P1
Message no. KD 503

Diagnosis
During settlement, the system puts the sender debits into groups (assignments), which are settled using the same settlement cost element. The settlement assignment is made in the allocation structure, which is stored in the settlement rule for the sender (under settlement parameters).
Cost element 5272310 cannot be assigned to a settlement cost assignment in allocation structure P1, and therefore it cannot be assigned to a settlement cost element.

Procedure
Possible solutions are as follows:

If the posting under cost element 5272310 was made to the sender because of an incorrect entry, and you can reverse the posting, and do not need to update the allocation structure. You only need to reverse the incorrectly assigned posting before repeating the settlement. Exception: For an investment measure with a line item settlement, you need to extend the allocation structure, even after the reversal.
If the posting was made correctly, you can do the following:
a) You can assign a different allocation structure to the sender: In the master data maintenance for the sender, choose “Settlement rule -> Goto -> Settlement parameters” and then enter a different allocation structure.
If necessary, also check whether the correct allocation structure is entered in the settlement profile. The allocation structure is defaulted in the settlement profile when you create sender master data or when you maintain the settlement rule.
You can update allocation structure P1

And here the solution :
Solution :
Alternatif #1. Attaching G/L account into allocation structure
Procedure : 1. Reverse all transaction causing error related to WBS and G/L account.
2. Attach G/L or cost element into allocation structure.
Path IMG :
Project System > Costs >Automatic and Periodic Allocations >Settlement > Settlement Profile > Create Allocation Structure (T-Code: no specific T-Code only ‘general’ SPRO)
3. Settle WBS Element using T-Code CJ88
Note: Not Recommended

Alternatif #2. Reverse the transaction causing error in one period on each transaction.
Procedure : 1. Reverse the transaction using t-code MBST.
2. If not possible using journal correction t-code FB50.
3. Settle WBS Element using T-Code CJ88.

Note : to see status GL Account posting manual / automatic use t-code FS00

2 comments August 4, 2007


Top Posts

Categories

RECENT POSTS

Recent Comments

Archives

Blog Stats

Meta