Special Purpose Ledger, restrict transactions

[former_member471229]

Hi, we are implementing a SPL to capture transactions between company codes.  In the configuration we can limit the types of transations, but not sure how to limit transactions so that we only have those between company codes.

For example, if a settlement is run we would want to capture the activity KOAO, but if the sender and receiver object are both in company A, then we do not want this transaction.  If the sender and receiver are in different company codes, then we want to capture this in our SPL.  The user exits available seem to be only for field movements, not an entire transaction.

Any suggestions?

Thanks

Kory Squire

[tonygaron · Accepted solution]

Hi Kory,

     We have used the user exits in SPL to code specific rules.  We copied the standard SAP report RGGBS000 to a Z program and assigned it in TCode GCX2.  The user exits are assigned in the SPL "Change Ledger" TCode GCL2 in the "ledger selection" under the "Transaction Assignment".  The user exit can be coded to return false or true depending on the fields in the header ACCHD or the line items ACCIT_GLX.

     However, I looked a little more at the fields available at the time of posting, and I don't see anything that indicates a cross company code posting.  If this is true, you may have to set up the SPL ledger configuration for the transactions as "2 - Activity/Ledger is only posted at subsequent posting" and do a look up the BKPF table for BPKF-BVORG field in the user exit.  The SPL load program GCU1 would have to be run periodically in this case.

     Hope this gives you some ideas to work with.

     Tony Garon

[former_member471229 · Accepted solution]

Hi Tony, thanks for the response.  After I posted this I found the set up for Ledger Selection.  Within there I was able to create a rule that checks coep-bukrs against coep-pbukrs.  If they are not equal then it is a cross-company code transaction.

Thanks for the help!

Kory