3395715 - Wrong G/L Account Is Derived For Production Order Confirmation

The resource X has been maintained in the production order, and the resource is mapped to G/L account: AAA.

There is a service Y maintained in the master data of this resource X, and the service is mapped to G/L account: BBB.

In the journal entry of production order confirmation, for the resource line, see it's posted to G/L account: AAA. 

(X represents the resource ID. Y represents the service ID.)

(AAA and BBB represent different G/L accounts.)

SAP Business ByDesign

1. Go to General Ledger work center.
2. Go to Journal Entries view.
3. Search for the journal entry ID. 
4. See that the G/L account used is AAA.
5. Why G/L account AAA is derived instead of BBB.

Although a service has been assigned to the related resource, there is no service maintained in the production confirmation document itself. If no service is involved in the document, then the G/L account is derived using the default entry in account determination for resource, which is G/L account AAA.

The journal entry derivation does not consider whether the a service has been assigned to a resource, instead it directly check whether the required service is used in the production confirmation or not. Only when the service itself appears in the production confirmation document, the related G/L account BBB will be considered in generating a journal entry.

Assign a service to a resource and also to the production model. Then the G/L account BBB which is directly related to the service can be brought to the production order and production confirmation. 

KBA 1917376- Unposted Production Confirmation - Default entry without acc. det. group: G/L account missing for services

production confirmation, journal entry, G/L account, resource, service  , KBA , SRD-FIN-GL , General Ledger , SRD-FIN-INV , Inventory , Problem