Functions and Features

Note

This Functions and Features page contains differing sections of useful, additional information and topics related to each app which may be of a functional or technical nature.

Bypass posting screen

You can by-pass the posting screen in the General Postings app for both posting via the basket or posting immediately if you don't need to enter any material document header fields. This is achieved by removing ALL the fields in the AMD from the INPUT_****_POST screen. The system then default the system date for both the posting and document date for the material document.

Note

If you want or need to enter header fields then, as of release 5.8.0, you can now add the header fields (i.e. those usually entered in the posting screen (INPUT_****_POST)) into the item input screen (INPUT_****_ITEM) and use the "post immediately" action. You are not able to use the basket functionality with these header fields.

Posting period closed for current date

This feature can be used generally in test SAP systems if it is required to add items to the basket in the General Postings app BEFORE being able to specify a posting date in the past. This is generally required when the open posting period has not been rolled over and so is not valid for today's date.

The posting date field PSTNG_DATE can be added to the INPUT_****_ITEM screens so that a date in the past can be entered on the screen and the item added to the basket. This does not store the date entered in the basket - it is only a way to allow items to be added to the basket.

When the basket is posted then the user will have the usual header details determined on the posting screen (if the AMD for INPUT_****_POST is setup) where they can edit the posting date if allowed or if the posting screen is being by-passed then the system will attempt to use today's date as default.

Displaying of stock on hand

For displaying the stock quantity in General Postings the following setup is required:

1. For standalone General Postings or jumps to General Postings, the fields ORIG_QNT and ORIG_UOM can be used in the AMD together with the field class /TCTM/WM_APP_513_FIELDS. This will display either the IM stock level or if the LQUA storage bin is provided, the IMB stock level (for that bin) or if the LQUA storage bin AND storage type is provided, the WM stock level (for that bin).

2. To support this feature, in the standalone version of General Postings, it is now possible to define the storage bin field LQUA-LGPLA (to be used for WM and IMB) and the storage type LQUA-LGTYP (for WM use only) in the INPUT_xxxx_MATERIAL screen - then when on the INPUT_xxxx_ITEM screen the app will display the WM or IMB stock rather than the MB52 stock.

Note

This does NOT work for the "reservation" transactions and for this a different setup is required in AMD: the fields MB52-MENGE and MB52-MEINS together with field class /TCTM/WM_APP_513_FIELDS needs to be defined.

It is not possible to show any WM or IMB specific stock levels as the WM and IMB bins would be unknown since they can't be entered before getting to the screen INPUT_xxxx_ITEM.

Stock records (technical)

Developers should note the following for use in any custom field class or enhancements:

For items being processed in Inventory Management (IM) sotrage locations, the MB52 structure and table MB52_T will be added to GT_DTA and the LQUA records will NOT. For items being processed in Warehouse Management (WM) or IM Multi-bin (IMB) storage locations, the LQUA structure and LQUA_T table will be used to hold the stock data. This allows you to determine whether to use MB52 data or LQUA data depending on whether we are in IM or WM/IMB.