Ansicht
Dokumentation

PM_ACDOCA_SDM - Enrich Plant Maint. related fields for existing line items in ACDOCA

rdisp/max_wprun_time - Maximum work process run time   CPI1466 during Backup  
This documentation is copyright by SAP AG.

Purpose

Allows you to update all the Plant Maintenance (PM) related fields of ACDOCA records for Maintenance Orders that have Time Confirmation/ Goods Issue/ Goods Receipt/ MM-SRV postings. The update is only triggered when all the PM related fields of an ACDOCA record are empty.

Integration

Prerequisites

Make sure you have the authorization object 'FINS_MIG' assigned in your profile to execute the report. In addition to this, the report can only update the PM fields of ACDOCA if and only if, the below two criteria are met:

- The records have Time confirmation/ Goods Issue/ Goods Receipt/ MM-SRV postings.

- All the PM fields of these ACDOCA records are empty.

Defined fields

Main Work center: This is populated from the Sub-Operation/ Operation/ Order Header level.

Maintenance Order Planning Indicator, Priority Type, Priority, No of Superior Order: These are populated from the Order Header level.

Operation and Sub-Operation Number: These are populated from the posted documents which can be either Confirmations or Material Documents.

Equipment, Functional Location and Assembly: These are populated from the Sub-Operation/ Operation/ Order Header level. In case there is nothing maintained on a detailed level, the object number is taken from the next higher level.

Maintenance Activity Type: This is populated from the Order Header. In case of Operational Account Assignment (OAA), it is derived from the Operation.

Material Group: This is populated from the Reservation for planned consumptions. For Unplanned consumptions, it is derived from the Material Master data, when in addition OAA is active, then it is derived from the Operation.

NOTE: In case of archived Material documents, the PM related data cannot be updated for planned consumption with and without OAA. The update logic with OAA takes the field values from the Operation/ Order Header level and the update logic without OAA takes the field values (except Operation, Sub-Operation, and Material Group) directly from the Order Header.

Selection

The following fields can be filled with selection values in the Report:

- Ledger

- Company Code

- Fiscal Year

- Posting Period

- Document Number

- Order

The following checkboxes can be used to run the update separately for each scenario.

- Time Confirmations

- Goods Issue

- Goods Receipt

- External Services Management (MM-SRV)

When any of these checkboxes are selected, the relevant records are updated with PM related data. The Overhead costs maintained in the Costing Sheet are considered when Time Confirmation and Goods Issue checkboxes are selected.

- Test Run: Use this checkbox to run the update in test mode.

- Display: Use this checkbox to display the (to be) updated ACDOCA table where the PM fields are highlighted in 'Green'.

- Layout: A variant of your choice can be saved and reused by replacing the default variant '/layout' with the newly saved one. This layout will be then applied to the ACDOCA display table.

- Max Records: This parameter allows you to run the update in iterations of the maximum number of records specified here. If this parameter is not supplied, it is defaulted to 50,000 records, that will be processed per iteration.

Additionally, the display of the output table is only possible if the number of records fetched by the report for an update is equal to or less than the 'Max Records' supplied on execution of the report.

Standard Variants

Provides a standard variant 'layout' that includes all the relevant fields of ACDOCA. This layout is applied to the ACDOCA display table which can be viewed after executing the report.

Output

The updated ACDOCA records are displayed in an output display table where the PM fields are highlighted in 'Green'. This table can only be viewed if the report is executed with the 'Display' checkbox.

The logs are displayed after the update that will clearly indicate the number of ACDOCA records affected by an execution. If errors occur during an update, the log will display all failed ACDOCA entries stating their primary keys that are seperated by a slash '/'.

Activities

Please note the following before triggering the update:

- Once the update has been triggered in 'Productive Mode', please be aware that a 'Revert Back' is no longer possible.

- For a larger number of line items, execution of the report in background is possible.

BAL Application Log Documentation   BAL_S_LOG - Application Log: Log header data  
This documentation is copyright by SAP AG.

Length: 4985 Date: 20240520 Time: 095038     sap01-206 ( 54 ms )