Ansicht
Dokumentation

/ISDFPS/BADI_PM_CO - BAdI: Define and Check CO Data Transfer

RFUMSV00 - Advance Return for Tax on Sales/Purchases   General Data in Customer Master  
This documentation is copyright by SAP AG.

You can use this Business Add-In (BAdI) to check and influence the CO data transfer during the distribution of maintenance objects (orders, notifications, functional locations, and equipment). The behavior is controlled using the structure PM_CO_DATA_X. If the value 'X' is filled in a field in this structure, the value of the assigned data field is transferred for the calling program. A SPACE or an initial value indicates that the value of the assigned data field is not transferred for the calling program. Below is a list of the maximum number of fields that can be influenced, provided that they are known for the calling object or program:

WBS_ELEM	WBS element of the additional data for the maintenance order
LOC_WBS_ELEM	WBS element of the location and account assignment data
ASSET_NO	Main asset number
SUB_NUMBER	Asset subnumber
SETTLORDER	Settlement order
RESPCCTR	Cost center responsible
PROFIT_CTR	Profit center
COSTCENTER	Cost center
STANDORDER	Standing order number
SUPERIOR_NETWORK	Network number of the superior network
SUPERIOR_ACTIVITY	Activity number in the network and standard network

The BAdI is shipped with a default implementation. In the default code, the following is implemented for the distribution scenarios in Maintenance:

• New or changed object (such as an order) is distributed from the central system to the decentralized system:

CO data is deleted and therefore not transferred to the decentralized system.

• New object (such as an order) was created in the decentralized system and distributed:

CO data from the decentralized system is transferred to the central system.

• Object (such as an order) was changed in the decentralized system and distributed:

CO data <> SPACE from the decentralized system is transferred to the central system.

In this way, data maintained in the central system for the object types "order" and "notification" is overwritten only if the data comes from the decentralized systems with content. Values maintained in the system for the object types "equipment" and "functional location" are not overwritten or deleted.

The BAdI call is encapsulated by the function module /ISDFPS/PM_CO_DATA_CHK. This function module is called by the order, notification, equipment, and functional location modules /programs. Below is a list of the Co data that can be deleted.

Order: The following fields can be influenced:

WBS_ELEM	WBS element of the additional data for the maintenance order
LOC_WBS_ELEM	WBS element of the location an account assignment data
ASSET_NO	Main asset number
SUB_NUMBER	Asset subnumber
SETTLORDER	Settlement order
RESPCCTR	Cost center responsible
PROFIT_CTR	Profit center
COSTCENTER	Cost center
STANDORDER	Standing order number
SUPERIOR_NETWORK	Network number of the superior network
SUPERIOR_ACTIVITY	Activity number in the network and standard network

Notification: The following fields can be influenced:

WBS_ELEM	WBS element of the additional data for the maintenance order
ASSET_NO	Main asset number
SUB_NUMBER	Asset subnumber
STLMTORDER	Settlement order
COSTCENTER	Cost center
STDGORD	Standing order number

The following applies for orders and notifications: If the value of the update indicator in a CO data field (parameter PM_CO_DATA_X => reference structure /ISDFPS/PM_CO_DATA_X) is initial, the corresponding data field is also initialized, which means that any transferred values are deleted, that is, they are not posted on the receiving side.

Functional location and equipment: The following fields can be influenced:

WBS_ELEM	WBS element
ASSET_NO	Main asset number
SUB_NUMBER	Asset subnumber
SETTLORDER	Settlement order
COSTCENTER	Cost center
STANDORDER	Standing order number

When an object is posted to the decentralized system, distribution (the value is deleted or posted from the source system) is carried out in accordance with the values returned by the BAdI in the parameter PM_CO_DATA_X.

When a functional location is posted to the central system, existing values cannot be deleted or overwritten. The values are posted as they are received, with the exception that existing values in the central system are not overwritten.

The following parameters are transferred to the interface module /ISDFPS/PM_CO_DATA_CHK or BAdI /ISDFPS/PM_CO_DATA:

• ACT_TYPE (Activity category)

• H (Add)

• V (Change)

• BUS_OBJECT (Business object: order, notification, functional location, equipment)

• WO (Order)

• NO (Notification)

• FL (Functional location)

• ET (Equipment)

• BUS_TRANS (Business transaction: distribution, relocation, and so on; currently not used)

• PM_CO_DATA (CO data: list of the Co data to be influenced)

The following parameter is returned:

• PM_CO_DATA_X (update indicator for CO data: for each field to indicate whether it is to be deleted or changed)

If you want to implement a separate logic for the objects listed above, you have to create a BAdI implementation to override or replace the default code.

STANDORDER

STANDORDER

The function delivered in the standard SAP system is configured as the default code for this BAdI.

STANDORDER

STANDORDER

SUBST_MERGE_LIST - merge external lists to one complete list with #if... logic for R3up   rdisp/max_wprun_time - Maximum work process run time  
This documentation is copyright by SAP AG.

Length: 8963 Date: 20240508 Time: 204527     sap01-206 ( 89 ms )