2020-03-03 2151987

2151987 - CIF DELTA REPORT: error 152 for Planned

Orders
SAP Knowledge Base
Version 2 Type
Article
Master
Language English English
Language
Release
Released to Customer Category Problem
Status
SCM-APO-INT-CCR-IP (In-House
Component Released On 05.07.2019
Production)

Please find the original document at https://launchpad.support.sap.com/#/notes/2151987

Symptom

In SCM system, when running CIF Delta report for planned orders, the error /SAPAPO/CIF152 (Order does
not exist in APO) is displayed

Environment

• SAP ERP and SCM system

• Release Independent

Reproducing the Issue

1. Run the CIF Delta report using the T-code /SAPAPO/CCR

2. Enter Partner system, Material (optional) and Plant (optional)
3. Mark Flag ‘Planned orders’
4. Execute
5. CCR reports error that the planned order is missing in APO (/SAPAPO/CIF152)

© 2020 SAP SE or an SAP affiliate company. All rights reserved 1 of 10

2020-03-03 2151987

Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to
real data is purely coincidental.

Resolution

The following are the possible causes and solutions for the error

• Integration model

There needs to be an active integration model for the material, plant and the object planned orders

a) Execute T-code CFM5 in ECC system and check the objects - material, plant and planned order and then

enter the material and the location for the order in the corresponding object fields and execute the model

© 2020 SAP SE or an SAP affiliate company. All rights reserved 2 of 10

2020-03-03 2151987

b) Select the material and press the ‘Details’ button and check if there are any models present along with a
tick mark in green

• MARC-APOKZ for the header material

The indicator APOKZ in the material master table MARC corresponds to the material relevance for APO, this

© 2020 SAP SE or an SAP affiliate company. All rights reserved 3 of 10

2020-03-03 2151987

indicator needs to be set which again indicates that the

material is present in active integration model

a) Execute T-code SE16 and enter table MARC

b) Fill the values for the field material and plant and then execute

c) Check the indicator for the field APOKZ is filled is must be set to “3”

d) You can also execute the report RAPOKZFX to fix the inconsistencies with this field

e) Check if the integration model for the planned order is pointing to the correct connected SCM system, in
case there are many SCM systems

connected to your ECC system. Check note 2143306 for the same.

• Settings for Logs

Ensure that your user has the proper settings to log the queue that is transferred between the ECC and SCM
system.

a) In ECC system, T-code CFC1 maintain the queue type (inbound or outbound) that determines where the
queues are processed

b) In ECC system, maintain an entry for your user in the T-code CFC2 in order to log the queue

c) In APO system, in T-code /SAPAPO/C2, maintain the following entries:

I. Queue type (inbound or outbound)

II. Error handling method (Post processing or strict queues)

d) In APO system, in T-code /SAPAPO/C4 maintain the following entries

I. Detailed logging for your user in order to log the queue

II. Event recording to ‘Default’ or ‘collect changes’

e) Enter T-code SMQ1 to check the outbound queues and T-code SMQ2 to check the inbound queues

• Resend the order and check the logs

Resend the order again from ECC to APO and then check the logs and queues with error which is blocking
the planned order to reach APO system.

There are two possible ways to resend an from ECC to APO system

a) Resend the affected planned order to APO using the report RCIFORDT in ECC system

I. Enter transaction SE38 and then execute the report RCIFORDT

II. In the selection field enter the affected planned order, the logical system where the order needs to be sent
and then execute the report

© 2020 SAP SE or an SAP affiliate company. All rights reserved 4 of 10

2020-03-03 2151987

b) Resend the affected planned order to APO using the CIF Delta report in APO system

I. In APO system, execute the T-code /SAPAPO/CCR and run the report for your previous selection

II. In the result screen select the order and press ‘Send to APO’ button and then press ‘Iterate’

After the orders are resent from ECC to APO system the queues and logs are checked. There are various
places where these can be checked

a) If the error handling method is post processing then :

I. Execute transaction /SAPAPO/CPP

II. Enter the logical system which is the connected ECC system and execute

© 2020 SAP SE or an SAP affiliate company. All rights reserved 5 of 10

2020-03-03 2151987

III. There is an index node on the left side of the screen where we can choose your data and double click on it

IV. The corresponding order appears on the right side of the screen

V. Select the order and press the button ‘Send to APO’

VI. There is a line that appears in the ‘Object processed in this session’ below

VII. Select the line and refresh it and check for errors

b) If the error handling method is strict queues then check ECC outbound (T-code SMQ1) or APO inbound
(T-code SMQ2) for the error queues

c) Execute the T- code /SAPAPO/C3 to check the logs in APO system

© 2020 SAP SE or an SAP affiliate company. All rights reserved 6 of 10

2020-03-03 2151987

Execute the T-code SLG1 to check the logs in ECC system

© 2020 SAP SE or an SAP affiliate company. All rights reserved 7 of 10

2020-03-03 2151987

• System Copy

If a system copy is done from one landscape to another then check if the common procedure for the system
copy of an SAP Solution landscape is been implemented correctly

according to note 886103

• ECC checks

a) If the order transfer program has been carried out through jobs, then check for the job status for failure or
success. If failure then determine the root cause and execute the job again

I) In ECC system, execute T-code SM37 and enter the job that was scheduled for the order transfer

© 2020 SAP SE or an SAP affiliate company. All rights reserved 8 of 10

2020-03-03 2151987

II) Check the job status for 'cancelled' or 'Finished

III) If there are any cancelled jobs, then select the job and click on 'job log' to find the detailed information and
to solve the issue

b) Dumps

© 2020 SAP SE or an SAP affiliate company. All rights reserved 9 of 10

2020-03-03 2151987

In ECC system, execute T-code ST22 and check of there are any dumps in the system that may be caused
to do performance or system failure, corresponding to the user and the date of transfer

Keywords

CCR, error 152, planned order, missing in APO, CIF, and Delta report

Products

SAP ERP 6.0

SAP Supply Chain Management 2005
SAP Supply Chain Management 2007
SAP Supply Chain Management 4.0
SAP Supply Chain Management 4.1
SAP Supply Chain Management 7.0
mySAP ERP 2004

Other Components

Component Description

SCM-APO-INT-CCR CIF Compare and Refresh

SCM-APO-INT Interfaces

This document refers to

SAP Note/KBA Title

Controlling the Initial Transfer of Planned Orders

Integration of planned orders

Determination and Correction of Inconsistent Transaction Data

Creating SNP Planned Orders from SAP ERP

Terms of use | Copyright | Trademark | Legal Disclosure | Privacy

© 2020 SAP SE or an SAP affiliate company. All rights reserved 10 of 10