Ansicht
Dokumentation

OALE_DSTSCN_DSTCNTRK - Purchasing: Distributed Contracts

rdisp/max_wprun_time - Maximum work process run time   ROGBILLS - Synchronize billing plans  
This documentation is copyright by SAP AG.

In this section of the IMG, the settings are described which must be maintained for purchasing if contracts are to be distributed.

Consistency checking

The function in this chapter checks the consistency of your settings.

We recommend that you make use of this consistency checking when you make the relevant settings.

Execute the function in the purchasing system. This allows you to check whether the settings between the systems are correctly maintained for the message types that are required. Check the application consististency for the decentral sales systems and the 'BLAORD' and 'BLAOCH' messages.

If you double-click on one of the lines of the consistency check log, you will enter the corresponding Customizing transaction and you can make the necessary settings there.

Before you can do this, it is necesssary that you have maintained

partner profiles in all the relevant systems.

Settings which must be made in the application so that distribution can be carried out are described in the MM release notes and in the IMG for Purchasing.

Make the following settings:

1. Use a new contract category for the distributed contracts. Contract distribution is controlled via the contract category, that is, the contract category in the customer model determines the systems to which contracts with a certain contract category are distributed (Specify document types and number ranges).
2. During contract distribution, you will have to coordinate the number ranges (Specify document types and number ranges):

• in every remote system, the number range for external number assignment must be set up for every contract category affecting distribution in such a way that it includes the number ranges for both the internal and external number assignment of the central system.

• in the central purchasing system, the number range for the local release orders must be maintained for every contract category affecting distribution.

1. Contract distribution in the central system is carried out via message control:

• use message type VNEU for contract distribution. Message type VNEU is defined in client 000. Copy message type VNEU into other clients, if necessary.

• So that message VNEU is proposed via message determination during contract entry, message determination procedure RMBEV1 must be assigned for contracts.

• The VNEU message has to be assigned to the RMBEV1 schema. The assignment is defined in client 000. Copy the assignment to the corresponding clients where necessary.

1. Also create a message condition record for message type VNEU with the key combination "Output determination in Purchasing: document type".

Enter the following parameters for the message condition record:

1.,,Document type = contract type relevant to distribution

2.,,Transmission medium of message = 'A' (ALE)

3.,,Shipping date = '4' (immediately)

The message condition record is created in the menu function Logistics -> Materials management -> Purchasing -> Master data -> Messages -> Outline agreement -> Create.

1. For the following message types you have create partner profiles for this scenario:

Mess. type	Comment		Cent.Purch	Dec.Purch.
BLAORD	Create contract		(output)	(input)
BLAOCH	Change contract		(output)	(input)
BLAREL	Communicate rel.orders	(input)	(output)

1. If you made the settings yourself, you can check the consistency of the control data in the central system for the message types BLAORD and BLAOCH. Refer to the ALE Implementation Guide: Communication -> Check consistency against the customer model.

For this scenario, the following data must be distributed to all participating systems:

(input)

• material master

• vendor master

(input)

Description	Object
Company code	V_T001
Purchasing organization	V_T024E
Purchasing group	V_024
Contract type	OMEF
Incoterms	V_INC
Terms of payment	V_T052
Shipping instructions	V027A
Tax indicator	FTXP

Tax indicator

In the remote systems, maintain the assignments for the following standard tasks:

Standard task	Description
BLAORD_Error
BLAOCH_Error

In the central system, maintain the assignments for the standard task:

BLAREL_Error

Standard task

The customer enhancements in Purchasing are implemented as customer exits. To find out exactly how to use each customer exit, please refer to the documentation of the component in question.

The following customer exits are available:

• Contract distribution (message type BLAORD/BLAOCH)

• Outbound processing

Customer exit '001' in enhancement 'MM06E001' for entering data in the extension type in the control record of the Intermediate Document.

Customer exit '002' in enhancement 'MM06E001' for entering data in the data segments in the IDoc.

• Inbound processing customer exits '001', '002', '003' in enhancement 'MM06E002' for the evaluation and import of IDoc data.

• Distribution of release order documentation (message type BLAREL)

• Outbound processing

Customer exit '001' in enhancement 'MM06E001' for entering data in the extension type in the control record of the Intermediate Document.

Customer exit '003' in enhancement 'MM06E001' for entering data in the data segments in the IDoc.

• Inbound Processing

Customer exit '004' in enhancement 'MM06E001' for the evaluation and import of IDoc data.

Standard task

If contracts are created with a purchasing organization which has no plants assigned to it (possible in central purchasing), then error message 06 794 might be issued: 'There is no work that could release from the contract item'.

You can control what type of message (warning or error) is issued or whether a message is to appear at all in the Implementation Guide Materials management -> Purchasing -> Environment data -> Determine attributes of the system messages.

PERFORM Short Reference   ABAP Short Reference  
This documentation is copyright by SAP AG.

Length: 9153 Date: 20240523 Time: 194514     sap01-206 ( 97 ms )