Optional : 999 Lineitems

SAP has a well-known limit of 999 lineitems per journal document. Customers often need to post journals with thousands of lineitems.

The Promenta solution enables posting journals with more than 999 to be automatically split into several documents that have less than 999 lineitems.

Note : This functionality is called “999 linitem limit” however in reality the limit may be less if you are posting tax where SAP will generate additional lineitems.

In Promenta the limit is configurable for any number of lineitems up to 999. Promenta recommend an initial limit of 850.

Functionality

The 999-split is activated or deactivated at global level (all processes) or at the process code level. Process code level configuration takes priority over global settings. The actual number of lines to split on can be set here but a good default is 850 lineitems to ensure enough spare lines for any tax postings.

For each company code a balancing account must be setup which will be used to ensure each “partial document” balances .

From SP24-2 : You can define a default account used in all company codes instead of specifying an account for every company code. This is used only if a specific setting for a company is not maintained.

The original spreadsheet and any evidence uploads can be attached to the first “partial document” or all “partial documents”

Restrictions

The user may need to reorder lineitems to overcome some restrictions below.

The splitting does not take into account dependencies between line items. Hence you may need to ensure that linked lineitems are in the same document. This may be the case with several taxable lineitems that you want to calculate the tax on automatically.

Cross-company postings are supported to several company codes but each lineitem should have the relevant company code on every lineitem. If you do not do this errors will occur as the header company code may be used instead.

SAP documents splitting to COPA and other ledgers will occur but the user should ensure that each document split at the lineitem limit makes sense in its own right.

Balancing lineitems will be generated with posting keys 40/50 only.

Balancing items will balance document amounts, local amounts and group amounts (fields WRBTR, DMBTR, DMBE2) if relevant.

Balances calculated on document amount ( field WRBTR ) is used to determine if 40 or 50 is required regardless of balance in DMBTR, DMBE2 fields.

The entire journal must balance (ie all the thousands of lineitems must balance) for the splitting to be allowed. As such postings where there is a non-zero balance such a posting with net taxes are not supported. Ensure users do not have the “Calculate taxes on net amount” option set in FB00.

Configuration

Each Company code must have configuration indicating the balancing GL account and also the lineitem text for the generated balancing lineitems. If a company could is not in the configuration but a split is detected then an error will occur.

1. Global switch

ACTIVE=< ON/OFF >=< limit >. This is the global switch which activates the splitting (ON) or deactivates it (OFF). In addition the global limit is set here with a maximum value of 999. All settings separated by a =.

2. Company code settings

BUKRS=< company >=< GL account >=< lineitem text >. The GL account and lineitem text must be specified. The lineitem text cannot be translated in the current version.

Since SP24-2 : You can define a default company code configuration which is used when no individual company code is found. Hence if you use the same account number across all or many of your company codes you can define the default entry once.

To define a default company code association – use the fixed value _DEF as below:

BUKRS=_DEF=< GL account >=< lineitem text >.

3. Attachments

CONFIG=ATTACH=< FIRST/ALL > . This setting determines whether attachments should be stored on only the first split document (FIRST) or all (ALL) split documents. This is useful to limit SAP storage usage. Note that the small note attachments which provide linkage information are always attached to all documents. The field must be the technical name from BBSEG.

 

4. Coding block

FLD=_DEF=<FIELD>=<VALUE>

When the balancing line item is created it will have the balance amount and a text by default. If additional coding block values are required then they can be added . Each field is added on its own row along with the company code it refers to (or _DEF if it is global setting)

Example : 

FLD=_DEF=GSBER=CORP 

This will add business area (GSBER) value CORP to the balancing account.

Configuration Example

In the example below :

1) ACTIVE=ON=900

Meaning : Splitting is on and splits at 900 lineitems

In the example below :

1) ACTIVE=ON=900

Meaning : Splitting is on and splits at 900 lineitems

2) 
BUKRS=_DEF=110999=DEFAULT account if no individual company code specified
BUKRS=GB01=119991=text for SP99 split lineitem
BUKRS=0001=110999=text for SP99 split lineitem
BUKRS=P100=119090=text for SP99 split lineitem

Meaning : Default company indication _DEF is used to set the account number if no individual company code found
Companies GB01, 0001 and P100 are configured individually

3) CONFIG=ATTACH=FIRST

Meaning : Store attachment on first split document only

2)
BUKRS=_DEF=110999=DEFAULT account if no individual company code specified
BUKRS=GB01=119991=text for SP99 split lineitem
BUKRS=0001=110999=text for SP99 split lineitem
BUKRS=P100=119090=text for SP99 split lineitem

Meaning : Default company indication _DEF is used to set the account number if no individual company code found
Companies GB01, 0001 and P100 are configured individually

3) CONFIG=ATTACH=FIRST

Meaning : Store attachment on first split document only

Screenshot

Scroll to Top