Ansicht
Dokumentation

V_SCON_JP_POVALD - Define Criteria for Determining Subcontract Act-Relevant PO Items

ROGBILLS - Synchronize billing plans   RFUMSV00 - Advance Return for Tax on Sales/Purchases  
This documentation is copyright by SAP AG.

Define criteria used by the system to determine if certain purchase order items are relevant to the Subcontract Act.

According to the Subcontract Act, some companies shall report to the Fair Trade Commission certain purchase transactions with suppliers who are smaller in capital amount. The purpose is to protect the interests of smaller suppliers, ensuring that they receive payments from purchasers on time and transactions are fair.

When creating a purchase order for a supplier, you mark the items that you think are Subcontract Act relevant using a custom field that you have implemented. When you save the purchase order, the system checks if the unmarked items are Subcontract Act relevant automatically. If an unmarked item passes the check, a message appears, informing you about it. You then think about whether it should be marked as relevant or not.

In this configuration activity, you define the criteria against which the system checks unmarked items to figure out if they are Subcontract Act relevant when you save purchase orders.

To make the criteria work, you must also do the following:

• Implement a custom field for indicating Subcontract Act-relevant items in the Create Purchase Order - Advanced app.

• Configure your custom field, capital amount, and capital amount currency in the additional data of your company code.

• Maintain the capital amounts of your suppliers in their business partner master data.

You define the criteria (sets of conditions) according to the Subcontract Act. A condition set include:

• Account assignment category (required)

• Plant (required)

• Storage location (required)

If you leave this field blank, the system considers that you have selected all your storage locations.

• Material group

You can enter an asterisk sign (*) as a wildcard or a material group ID containing this sign. For example, 4375* means all material groups whose material group IDs begin with 4375.

• Material number

You can enter an asterisk sign (*) as a wildcard or a material number containing this sign. For example, 99* means all materials whose material numbers begin with 99.

• G/L account

You can enter an asterisk sign (*) as a wildcard or a G/L account containing this sign. For example, 32000* means all G/L accounts whose G/L account numbers begin with 32000.

• Minimum net item amount and its currency

You must assign a sequence number to each condition set. By doing so, you prioritize the condition sets. Smaller sequence numbers represent higher priority. The system performs relevance checks according to the sequence of condition sets, as follows:

1. It checks a purchase order item against the condition set with the smallest sequence number.
2. If the item matches the condition set, then the check completes. Otherwise, the system continues checking the item against the next condition set in the sequence.
3. The system follows the cycle described in step 2.

Note:

• You can use sequence numbers from 1000 to 4999 only.

• It's likely that multiple condition sets apply to the same purchase order item at the same time. Be careful when assigning sequence numbers to such condition sets. Assign smaller sequence numbers to the condition sets that should have priority.

You can also specify the type of the message that appears when users save a purchase order with items that have passed the relevance check but are not marked as Subcontract Act relevant. The available message type options include Error and Warning. The message type determines what users can do in that case.

You can find from SAP Help Portal comprehensive documentation about relevance checks on purchase order items. Do the following:

1. Go to https://help.sap.com/viewer/s4h_ce_japan.
2. On the top left corner, select your release.
3. From the navigation pane on the left, select Sourcing and Procurement -> Operational Procurement -> Purchase Order Processing.

Fill RESBD Structure from EBP Component Structure   SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up  
This documentation is copyright by SAP AG.

Length: 4788 Date: 20240523 Time: 184652     sap01-206 ( 83 ms )