Skip to Content

Special Purpose Ledger, restrict transactions

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

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • Best Answer
    Posted on Jan 09, 2014 at 05:55 PM

    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

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.