Tags: spro

Duplicate Sales Order Check

PO Number field (VBAK-BSTNK) in Sales order contains customer’s order reference number. To avoid raising duplicate order for a customer SAP can be configured to check duplicate PO numbers. This blog highlights where in configuration you can activate this duplicate order check and which customer enhancement you can implement to check duplication during inbound IDoc processing.

Read More →

Number Range Enhancement for Sales Order, Billing, Delivery and Shipment

Configuration of Number range in SAP is can be only done on document types. This poses limitation that one can only have sequential number based on document types. In case, there is a legal requirement to maintain sequential number of documents based on other parameters for example, customer or country then this cannot be achieved using SAP standard configuration and needs enhancements. Fortunately, SAP has provides exits specifically for this purpose.

Read More →

Number Range Setting for Sales Order, Billing, Deliveries and Shipment

spro number range snro sales document order type

Number range in SAP is used to across modules to automatically number documents as and when they are created. Number range contains one or more intervals, each one of them define range of number and stores current value of counter. Each range is assigned or used to number a specific type of document for example a Sales Order, Deliveries, Billing document and so on. When these documents are create SAP reads assigned number range object and interval to read current value counter, which is then assigned to the new document, and then counter is increased by one. This way documents created are always in sequence, except when number range is buffered where gaps can occur. Refer How the Number Range Buffer Works for more detail.

Read More →

Enhance SPRO Structure – Adding Node to SPRO

sap spro enhance structure sap

Over the course of Implementation you would define many customising tables. I am sure you will document them well but best place to place these customising is in SPRO. In this particular example we have implemented enhancement in shipment screen to make forwarding agent mandatory and there is a customising table which is defined to control on which shipment types this check will be active. Best place to put this customising table is SPRO under node where consultant will create new shipment type. This way, in future, when consultant create new shipment type they will also review if mandatory setting needs to be active on new shipment type created.

Read More →