Error text

Cause

:/SAPAPO/STOCK:012 0000000000000000000000000000000043000109 Error with stock for material 43000109 in 0075 location 0075

04.01.2012 date comes after end of valid factory calendar (please correct)

A planned item has been planned for a time period that is not within the factory calendar No relationships have been maintained within either the PPM or master recipe

Activity net is not found

An error occurred while setting up a connection to No connection to LiveCache could be "LCA". - No Log was found establshed The MASTERDATA integration model for this APO indicator for material 000000000000430849 / product is not active. Therefore the APO plant 0019 is not active indicator is not set.

The material/location combination has not had APO indicator for material 000000000007801882 / an external planning MRP type allocated to it plant 0058 is not active within R/3 material master Connection closed

There is either no valid integration model available or there is a severe BASIS problem

connection closed - Changes to Matl Master

There is either no valid integration model available or there is a severe BASIS problem

connection closed - External procurement

There is either no valid integration model available or there is a severe BASIS problem

connection closed - In-house production

There is either no valid integration model available or there is a severe BASIS problem

connection closed - Manual reservations

There is either no valid integration model available or there is a severe BASIS problem

connection closed - No log was found

There is either no valid integration model available or there is a severe BASIS problem

connection closed - No log was found (Plan/Production Orders)

There is either no valid integration model available or there is a severe BASIS problem

connection closed - No log was found (POs)

There is either no valid integration model available or there is a severe BASIS problem

connection closed - No log was found (Stocks)

There is either no valid integration model available or there is a severe BASIS problem

connection closed - Plan/Production Orders

There is either no valid integration model available or there is a severe BASIS problem

connection closed - POs

There is either no valid integration model available or there is a severe BASIS problem

connection closed - Sales order

There is either no valid integration model available or there is a severe BASIS problem

connection closed - Stocks

There is either no valid integration model available or there is a severe BASIS problem

Connection to liveCache failed

No connection to LiveCache could be establshed

Connection to liveCache failed - Message incomplete (seriousness, area or number missing) No connection to LiveCache could be establshed

Customer 23376 has been assigned order block: Marked for Deletion

The customer quoted has been marked for deletion within the connect R/3 system

Customer demand 000000 0000 : Simsession conflikt in /SAPAPO/DM_SL_DOC_I

Customer demand 000000 0000 Simsession conflict in /SAPAPO/DM_SL_DOC_INBOUND

Customer Demand E0080105501 000010 0000: IIVECACHE problem, return code = 34 Customer demand G0000206180 000010 0001 : Product does not exist Customer demand L0000427070 000010 0001 : Product 434471 for location CU0000032411 not avail Message no. /SAPAPO/SALES 501 Customer demand N0080260482 000030 0000 : Do(es) not exist, cannot be cha Customer demand N0080449086 900001 0000 : Demand successfully added Customer demand N0080449086 900002 0000 : Already exist(s), cannot be added Customer demand N0080449086 900002 0000 : Do(es) not exist, cannot be changed The "ship to" party was changed in the order header which leads to the problem that the connection between the order in R/3 and the corresponding order in APO is lost.

Error during creation; GUID: FpzzfUunCXJX0000ZNgdKm FpzzfkunCXJX0000ZNgdK

An order could not be scheduled in APO. This can have the following causes: usually this happens when - you have not entered times for the downtime phase - you are reducing the process order quantity and thereby scheduled dates in a way that the operation time falls below a couple of seconds. APO cannot schedule the order. other reasons are: - You have not maintained a working time or a capacity for the resource. - You have made settings for an activity in the Production Process Model so that the activity cannot be interrupted by breaks. If the activity is longer than the working time between two breaks or between two non-working times, the system cannot schedule the activity. - The maximum intervals between activities that you have maintained in the Production Process Model are too short. The system cannot schedule the order without violating these maximum intervals. Error in scheduling An order has been unable to scheduled within Error in scheduling of an order - No log was found R/3 Error whill calling COM routines via application program (return code = 148) Error whill calling COM routines via application program (return code 215) In R/3 an order is completed (TECO) or confirmed in R/3 and R/3 sends a message via CIF to APO to delete or update the order there. This error occurrs if the order cannot be found in APO anymore.

Error whill calling COM routines via application program (return code 248)

Error whill calling COM routines via application program (return code 258 A stock element is sent to APO and it already exists there. If the 'Create new receipt elements' indicator is being used in the ATP check and if stock already exists on the checked customer individual segment, this causes the COM error with return code 54.

Error whill calling COM routines via application program (return code 54)

Fiscal year Variant NC is not maintained for calendar year 2007

Inbound OA2PRRC102: No IModel active for cat. Planned orders, filter obje

Planning has been attempted within a fiscal calendar year that has not been opened for planning The MOVEMENTS integration model for this product is not active or does not include this product. The product might not be in the integration model because the MRP type (on MRP 1 tab) has changed from eternal (X0/X1) to internal planning. Another reason might be that the status of the material was changed to Z4/Z5 and is therefore discontinued. In that case the material is not included in the integration model anymore. Material status was changed from external planning (X0/X1) to internal planning. Therefore an integtation model does not exist for this material. But there are still planning objects (planned orders, process orders, purchase orders, ...) in APO for this material.

Inbound OA2PRRC102: No IModel active for cat. Purchase orders and purch.r

Info record for vendor 100038117 and material 1632722 does not exist

The Info record for the vendor/material combination does not exist in R/3. Therefore R/3 cannot schedule the purchase requisition. Reasons: a) an import purchase order was not directed to the market HQ but directly to the plant b) the info record was never created

In-house production is not intended for material 12000093 status Pre-go d

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

In-house production is not intended for material status

The material/location combination has been given an mm/pp status that does not allow it to be planned

In-house production is not intended for material status Pre-go d

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

A material has been given an mm/pp status of "Discontinued" which is not a valid mm/pp status for planning Table fields were added and therefor the table Invalid adressing handle PXA 1.2944 im needs to be reactivated. It is a temporary programm SAPFSYSCALLS inconsistency between DataBase and Repository objects. Table fields were added and therefor the table Invalid adressing handle PXA 1.83184 im needs to be reactivated. It is a temporary programm SAPLFCIN inconsistency between DataBase and Repository objects. Table fields were added and therefor the table Invalid adressing handle PXA 1.864 im programm needs to be reactivated. It is a temporary SAPMSSYD inconsistency between DataBase and Repository objects. In-house production is not intended for material status under discontinuation

Invalid order Invalid ROLLBACK WORK in an update function module

There is an invlaid order

Invalid time interval Invalid use of change activity old_state/new_state not plannable Item 00010 of outline agreement 4600102303 flagged for deletion A contract is flagged for deletion and no new contract exists.

Item categories in agreement and requisition incompatible

There are inconsistencies between APO and R/3 purchase requisitions

Item in plant is discontinued Location 0100009446 does not exist Procurement relationship not created for 2 4600102348 000010 0017

A material has been given an mm/pp status of "Discontinued" which is not a valid mm/pp status for planning

Master data cannot be read in order 000010066780

An order has faield to be accepted by R/3 during a CIF transfer

Material 100284 not maintained by Purchasing

No R/3 purchasing master data has been maintained for the material

Material 12000257 cannot be taken from plant 0035 due to status "Pre-go d

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

Material 43002826 not maintained by Purchasing

Material 480587 0022. Status Under Discontinuation does not allow the planning run

There is no purchasing view maintained within the R/3 MDR for this material Materials are controlled by material statuses in R/3. Two statuses exist: - the cross-plant material status (Z1-Z5) on Basic Data 1 Tab - the plant specific material status (Z1-Z5) on Costing 1 Tab

A material has been given an mm/pp status of Material 7808468 cannot be taken from plant 0037 "Discontinued" which is not a valid mm/pp due to status "Discontin status for planning

Material 7822017 flagged for deletion

A material has been flagged for delteion within the R/3 MDR

Material cannot be taken from plant due to status "Discontinued"

A material has been given an mm/pp status of "Discontinued" which is not a valid mm/pp status for planning

Material cannot be taken from plant due to status "Pre-go decision"

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

Material cannot be taken from plant due to status "Pre-go decision". Status "Z2"

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

Material is flagged for deletion

A material has been transferred back to R/3 for planning but it has been flagged for deletion within the R/3 MDR

No Imodel active for cat. Purchase orders and purch. reqs

There is no active integration model for the category mentioned within the msg text

No Imodel active for cat. Purchase orders and purchase reqs for system OA3PRAPO1 (MRP Type = "PD")

There is no active integration model for the category mentioned within the msg text

No Imodel active for cat. Purchase orders and purchase reqs. (Deletion flag is set) - user JOBRUN no log. 001 RFC-R3CEA2 /SAPAPO/CIF_CONF_INBOUND CFCNF000010017281 21.02.2003 05:26:32 SQL error 600 occurred when executing EXEC SQL. No sales and distribution data maintained for material 7801288 No storage space available for extending table IT_2856 - No Log was found

There is no active integration model for the category mentioned within the msg text

BASIS error

An internal table sizing limit has been reached. Planned order existed within APO, converted to a process order (successful within R/3) but failed to send process order back to APO due to there being no PPM for material. How was the planned order created ?

Order 000010236721 Conversion of operations failed Order qty cannot be converted from CS to EA (unit of meas., mast. recipe) Order qty cannot be converted from CS to EA (unit of meas., mast. recipe) - List contains no data Order qty cannot be converted from CS to EA (unit of meas., mast. recipe) Processing status of order 0002073674: End processing of order Order qty cannot be converted from CS to EA (unit of measure, mast recipe) Production version 0010 Order type 1 Order type 1 Order number 0011736780 - source of supply -0042 Order type 1 Order number 0011912958 Order type 2 Order number 4500030974 Ordertype 2 Order no 4500040790 Item no 000010 Shced. No 0001 Ordertype 2 OrderNo 4500024501 ItemNo 000010 SchedNo 0001 (Product 7800575 for location 0042 not available)

There is a problem with a purchase requisition There is a problem with a purchase requisition There is a problem with a purchase requisition A purchase order is sent from R/3 to APO There is a problem with a purchase order

There is a problem with a purchase order

Pegarea for material 000000000007806995 location 0041 not available

A PPM has either not been found or could not be accessed for the material/location combination

Plan 0000000000120002580035002000000000260000 73501011 for product 1200025 There is an error with a PPM for a material

Planned order 1761367 is locked - Contains no data

More than 1 user has attempted to access a planned order at the same time.

Planned order is locked

More than 1 user has attempted to access a planned order at the same time.

Planned order is locked Production version 0010

More than 1 user has attempted to access a planned order at the same time.

Please enter net price

CIF has attempted to send a material to R/3 which does not have a net price

Please enter Purch. group

CIF has attempted to send a material to R/3 which does not have a purchasing group

Please insert net price Please specify the order deadlines in ascending order

CIF has attempted to send a material to R/3 which does not have a net price

PPM 0000000000120000940036001000000000260000 The internal PPM relationships are not valid 75501011: Activity net is not for the spcified PPM

PPM 0000000000242110010039001000000000260000 The internal PPM relationships are not valid 32201011: Activity net is not found for the spcified PPM

PPM 0000000000242130410039001000000000260000 The internal PPM relationships are not valid 32301011: Activity net is not connected for the spcified PPM

PPM 000010053975: Activity net contains a cycle

The internal PPM relationships are not valid for the spcified PPM. The PPM contains a relationship loop

PPM 43000362003900100000000026000036801011: Activity net is not - No log was found

The internal PPM relationships are not valid for the spcified PPM

Prodcution version required

There is no production version for a planned order to be placed on

Product 000000000007802428 does not exist

There is no production version for a planned order to be placed on

The product locaiton combination does not Product 12000971 for location 0035 does not exist exist within APO

Product does not exist

A product has been planned in APO but it does not exist with R/3.

The operation filter ensures that operations with zero duration are not sent to APO. If the confirmation is entered as a time ticket confirmation or as a confirmation in the order header without a separate start and end date being specified, the actual duration of the Production order 10019035 (In-house), source of operation is zero. The next scheduling copies supply the actual values to the planned values, which 260000600010220 , Product 40622174 , Location produces a planned duration of zero, which is 12 filtered out during the transfer to APO. This Error whill calling COM routines via application may result in the COM error if a phase with a program (return code 253) setup group key or a setup group category is sent to APO in a process order, but the next phase, which represents processing after setup, is filtered out due to the zero duration. A runtime phase in the PPM is not transferred to APO because the BOM is set inactive on the BOM header.

Production order 10024226 (In-house), source of supply 260000818010011 , Product 43001079 , Location 17 Mode with cover but no mode linkage via primary resource

There is an inconsistency within the PPM mode linkage

Production version 0009 for material 000000000024500192 is invalid for 00

The production version for this material is not valid for the date of the order.

Production version 0010 for material 24201012 in The production version for this material is plant 0035 is locked locked

Production version 0010 for material in plant is locked. Please correct the parameter in the Master The production version for this material is Recipe to "No Lock" locked

Production version 0030 for material 000000000007803837 is invalid

The production version for this material is not valid for the date of the order.

Production version required - Planned order 1366476 will not be converted

There is no production version for a planned order to be placed on

Production version required - Planned order will not be converted Purchase order was changed or deleted A purchase order was either changed or deleted

Screen output without connection to user - No log was found Possible GUI error.

Screen output without connection to user. Source not included in list despite source list requirement

Possible GUI error.

source of supply 0060 - Order type 2 Order number 4500049812

Order tpye 2 is a purchase order. There is an error with the source of supply (plant 0060 in this case)

SQL error -60 occurred when executing EXEC SQL.

SQL error -911 occurred when accessing table DBVM - No log was found

Status "Pre-go decision" of material 100286 does not allow external procu - List contains no data

A material has been given an mm/pp status of Z2 "Pre-go" which is not a valid mm/pp status for planning

A material has been given an mm/pp status of Status "Pre-go decision" of material does not allow Z2 "Pre-go" which is not a valid mm/pp status external pro for planning

Status "To be Archived" of material 12000806 does not allow external proc

A material has been given an mm/pp status of "To be archived" which is not a valid mm/pp status for planning

Status "Under Discontinuation" of material 24000062 does not allow extern

A material has been given an mm/pp status of "Discontinued" which is not a valid mm/pp status for planning

Status under "Discontinuation" does not allow the planning run

A material has been given an mm/pp status of "Discontinued" which is not a valid mm/pp status for planning

Substitution of Profit Center failed, no Sales Credit derived by CO-PA. Costing error

The ABAP/4 Open SQL array insert results in duplicate database records. r Transfer terminated after error occurred during transfer of order User MYDIKONJA already processing Purchase requisition 11571453

BASIS error

A purchase requisition is locked by a user 1) The purchasing view of this vendor is not maintained. 2) The order is invalid and should not exist in APO anymore.

Vendor 100038115 not yet created by purchasing organization CH10

Version 0010 does not exist for material

A production version does not exist for a material. It is most likely that a production version has been deleted in R/3 without the related APO PPM being made inactive

Version 0010 does not exist for material 7803099 in plant 0039

A production version does not exist for a material. It is most likely that a production version has been deleted in R/3 without the related APO PPM being made inactive

Version 0010 does not exist for material in plant

A production version does not exist for a material. It is most likely that a production version has been deleted in R/3 without the related APO PPM being made inactive

Version 0010 invalid for material 24230113 in plant 0035 With ABAP/4 Open SQL SELECT, the output area is too small. Work scheduling data of material 12000112 is not maintained. Prod Vers 0020 Work scheduling data of material 7808575 is not maintained

The production version for this material is not valid for the date of the order.

The work scheduling view for a material has not been maintained The work scheduling view for a material has not been maintained

Work scheduling data of material is not maintained

The work scheduling view for a material has not been maintained

You have no authorization for Transaction COR2

The user has no access to transaction COR2

Resolution procedure
Check the stock accuracy between APO and R/3 for this material/location combination Run /SAPAPO/CCR ir necessary but this should be a last resort. If the /SAPAPO/CCR transaction is run and this error remains, delete it. Use the APO application log (/SAPAPO/C3) to find this message. The product and PPM involved should be able to be found from the application log. If the plan is valid request that the GC DSP team opens the factory calendar for a longer period fo time. If this is not a valid planned item request that the planner re-plans the product Use the APO application log (CFG1) to find this message. The product and PPM involved should be able to be found from the application log. Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Reactivate the integration model and transfer/restart the hanging queues. Reprocess the queue entries First verify that this is a valid material for APO planning. If this is an APO planned material request that the MDR team change the MRP type for the material. If this product is not planned in APO it should be removed from all APO master data items and integration models. Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models

Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Inform BASIS with the R/3 and APO system names and ask for them to check the that the CIF connection is still valid. If the connection is live contact the GC DSP coordinator for them to check the integration models Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Verify that the correct customer is being used for planning. If this is a valid customer request the MDR to remove the deletion indicator. If it is not a valid customer move all pruchase requisitions to the new customer Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run

Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run

RLCDELETE TLB-VMI-SO from product

No action

Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run

Use the APO application log (CFG1) to find this message. The product, order and PPM involved should be able to be found from the application log. Attempt to reschedule the order in APO and reprocess the queue. If the error persists create an identical order and if this is successful delete the order that creates the error and then delete the queue block that relates to the original error. Use the APO application log (/SAPAPO/C3) to find this message. The product and PPM involved should be able to be found from the application log. Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved and get the full message

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved and get the full message

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved and get the full message

Verify that planning should be taking place within this year. To find the orders use /SAPAPO/RRP4 with a date range within this year only and all plants. If planning is not valid delete the orders. If planning is valid request that FI-CO open this fiscal period and reprocess the queue

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. Then use R/3 transaction CFM5 (Filter object search) to see if this material exists within an integration model. It either will not exist or will be within an inactive integration model. If this is a valid APO planned material include it within an integration model, activate it and reprocess the queue. If this is not a valid APO planned material delete all references to it within APO. Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. Then use R/3 transaction CFM5 (Filter object search) to see if this material exists within an integration model. It either will not exist or will be within an inactive integration model. If this is a valid APO planned material include it within an integration model, activate it and reprocess the queue. If this is not a valid APO planned material delete all references to it within APO.

Verify is this vendor.material con=mbination is valid. If it si request that the MDR team completes all master data within the MD

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the material/location involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Request that BASIS check the table and restarting CIF queue

Request that BASIS check the table and restarting CIF queue

Request that BASIS check the table and restarting CIF queue Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the material and location involved. Check within the product view to see if any orders do not have receipt elements to them. These are the ones at fault. Verify the plan. Give msg to BASIS to investigate

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the material and location involved. Check within the product view to see if any orders do not have receipt elements to them. These are the ones at fault. Verify the plan.

Ask the procurement team to verify the contract. If this is a valid procured material request that the contract is either extended or replaced with a new one. If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials and purchase orders involved. Ensure that the line items are common between APO and R/3. If there are inconsistencies that cannot be corrected it is suggested that the purchase order is cancelled and replaced with a new one. Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models

Use transaction COR3 (display production order) or MD13 (display planned order) to find the material and location combination. Return to APO for this combination and try to reexplode the planned orders that do not have receipt elements to them. Reprocess the queue. If the problem persists investigate if the master data is locked and if so remove the record locks. If msg persists create an identical order, if this is successful delete the initial order and delete the queue block. Check to see if the material is a valid material for planning. If it is OK request that the MDR team maintains the purchasing data within the MDR for the material. If this material should not be planned remove all occurrences of it within APO and any integration models

The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Verify that this is a valid procured item that is allowed for planning. If this is valid request that the MDR team complete the purchasing view for this material and then reprocess the queue. If this material should not be planned remove all occurrences of it within APO and any integration models

Verify that this is a valid planned material/location combination. If it is request that the material statuses are changed to allow p

The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models The material has been flagged for deletion within the R/3 MRD. Check to see if this is a valid APO planned material. If it is request that the MDR remove the deletion indicator. If this is not a valid APO planned material remove all occurrences of the material from APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. If this is a valid material for planning request that the MDR team removes the deletion indicator from the material. If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. Then use R/3 transaction CFM5 (Filter object search) to see if this material exists within an integration model. It either will not exist or will be within an inactive integration model. If this is a valid APO planned material include it within an integration model, activate it and reprocess the queue. If this is not a valid APO planned material delete all references to it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. Then use R/3 transaction CFM5 (Filter object search) to see if this material exists within an integration model. It either will not exist or will be within an inactive integration model. If this is a valid APO planned material include it within an integration model, activate it and reprocess the queue. If this is not a valid APO planned material delete all references to it within APO and any integration models. APO planned materials should not have an MRP type of PD, it should be X0 or X1

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. Then use R/3 transaction CFM5 (Filter object search) to see if this material exists within an integration model. It either will not exist or will be within an inactive integration model. If this is a valid APO planned material request that the MDR team removes the R/3 deletion flag, include it within an integration model, activate it and reprocess the queue. If this is not a valid APO planned material delete all references to it within APO and any integration models

Contact BASIS and give them the message text and the system id Request that the MDR team maintain the sales views of the MDR for the material Contact BASIS and give them the message text and the system id

Determine why an order exists for a material with no PPM. If this is a valid APO planned material the production versin=on in R/3 should be sent to APO and the queue reprocessed.

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved.

Verify that a valid PPM exists for the material/location combination. If none exist within APO, check to see if there are any production versions within R/3 for this combination. If there are not request that a master Use APO transaction /SAPAPO/SCC05, select the "Select plan through PPM", drop down the plan number cell, enter the material number and press ENTER. Search for the PPM name within the list. When found perform a consistency check on the plan and check the PPM validity dates. Go to the product view for this material and look for all planned orders without receipt elements. Reprocess these orders and then reprocess the CIF queues. Try MD12 in R/3 to change the planned order. If you gain access the lock has gone and the queue can be reprocessed. If the lock persists for some time use transaction SM12 to find the user locking the object. Try to contact the user to ask them to remove their lock or use transaction SM04/SM51 to remove the user lock if it has been there for some time. DO NOT delete the locks using SM12 as this does not prevent the original user saving their data. Instead this allows for data inconsistencies and is very dangerous Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material, location and order effected. Try MD12 in R/3 to change the planned order. If you gain access the lock has gone and the queue can be reprocessed. If the lock persists for some time use transaction SM12 to find the user locking the object. Try to contact the user to ask them to remove their lock or use transaction SM04/SM51 to remove the user lock if it has been there for some time. DO NOT delete the locks using SM12 as this does not prevent the original user saving their data. Instead this allows for data inconsistencies and is very dangerous Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material, location and order effected. Try MD12 in R/3 to change the planned order. If you gain access the lock has gone and the queue can be reprocessed. If the lock persists for some time use transaction SM12 to find the user locking the object. Try to contact the user to ask them to remove their lock or use transaction SM04/SM51 to remove the user lock if it has been there for some time. DO NOT delete the locks using SM12 as this does not prevent the original user saving their data. Instead this allows for data inconsistencies and is very dangerous

Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material effected. If this is a valid material for planning request that the MDR team enters a net price for the material on it's costing view. If this product should not be planned delete all references to it within APO and any integration models. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material effected. If this is a valid material for planning request that the MDR team enters a purchasing group for the material on it's purchasing view. If this product should not be planned delete all references to it within APO and any integration models. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material effected. If this is a valid material for planning request that the MDR team enters a net price for the material on it's costing view. If this product should not be planned delete all references to it within APO and any integration models. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material effected. Use /SAPAPO/SCC05 to perform a validity check on the PPM. Correct any errors that are found and then re-explode all orders that use the PPM by using the receipts/product view in APO for the output material and the locaiton of the PPM. Reprocess the queue entry. If all orders are invalid and have been moved to anotehr PPM delete the queue entries after attempting a reprocess. Use /SAPAPO/SCC05 to perform a validity check on the PPM. Correct any errors that are found and then re-explode all orders that use the PPM by using the receipts/product view in APO for the output material and the locaiton of the PPM. Reprocess the queue entry. If all orders are invalid and have been moved to anotehr PPM delete the queue entries after attempting a reprocess. Use /SAPAPO/SCC05 to perform a validity check on the PPM. Correct any errors that are found and then re-explode all orders that use the PPM by using the receipts/product view in APO for the output material and the locaiton of the PPM. Reprocess the queue entry. If all orders are invalid and have been moved to anotehr PPM delete the queue entries after attempting a reprocess. Use /SAPAPO/SCC05 to perform a validity check on the PPM. Correct any errors that are found and then re-explode all orders that use the PPM by using the receipts/product view in APO for the output material and the locaiton of the PPM. Reprocess the queue entry. If all orders are invalid and have been moved to anotehr PPM delete the queue entries after attempting a reprocess.

Use /SAPAPO/SCC05 to perform a validity check on the PPM. Correct any errors that are found and then re-explode all orders that use the PPM by using the receipts/product view in APO for the output material and the locaiton of the PPM. Reprocess the queue entry. If all orders are invalid and have been moved to anotehr PPM delete the queue entries after attempting a reprocess. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material and location effected. Go to R/3 transaction C223 and search for all production versions. If there are none check to see that this is avalid planned product. If is ensure that all master data is correct, especially MRP type should be X0 or X1. Ensure that there is a correct master recipe and BOM and create a production version. Include this version within an integration model and activate it. Then reprocess the queue. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material and location effected. Go to R/3 transaction C223 and search for all production versions. If there are none check to see that this is avalid planned product. If is ensure that all master data is correct, especially MRP type should be X0 or X1. Ensure that there is a correct master recipe and BOM and create a production version. Include this version within an integration model and activate it. Then reprocess the queue. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue.

Check APO Product master data using /SAPAPO/MAT1 to search for the material. If it does exist, reprocess the queue. If ti does not exist use R/3 transaction MM03 and display the MRP1 view for the material/location combination. If it does exist use transaction CFM5 to search to see if it is within an active integration model. If it is not, verify that this is a valid APO planned material. if it is include it within an active integration model. If this is not a valid APO planned material remove all orders that relate to the this material and re-CIF all PPMs that relate to it. If the product exists in R/3, with a XO/X1 MRP type, is within an active integration model but does not exist within APO, the chances are that the product location combination has been manually deleted from APO, which should not happen, and that the process order has been created in R/3, which should rarely happen. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material and location effected. If the material is a valid material for planning request that the MDR team complete all of the master data for it. A master recipe, BOM and production version will have to be created, included in an active integration model and then the queue reprocessed. Due to the length of time required for all of this it would be best if no planning was performed in APO. Make any PPMs for this product/location combination inactive.

Correct the order confirmation to ensre that it has a duration

Use APO transaction /SAPAPO/SCC05 and run a consistency check on the PPM. Ensure that each activity has "Mode linkage"defined. This should usually be linked by primary resource. Reprocess the queue Use APO transaction /SAPAPO/C3 (application log) to find this message and find the order effected. Once found, find the order dates. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are locked, correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are locked, correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the order effected. Once found, find the order dates. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material and location effected. Go to R/3 transaction C223 and search for all production versions. If there are none check to see that this is avalid planned product. If is ensure that all master data is correct, especially MRP type should be X0 or X1. Ensure that there is a correct master recipe and BOM and create a production version. Include this version within an integration model and activate it. Then reprocess the queue. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue.

Use APO transaction /SAPAPO/C3 (application log) to find this message and find the order effected. Once found, find the order dates. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. If no production version requires ensure that a master recipe, BOM and production version are created and included within an active integration model. Then reprocess the queue. Due to the time involved in creating all of this master data it is suggested that all APO plans using the invalid PPM are deleted and replanned on an alternative PPM and the invalid PPM is made inactive until all of the APO and R/3 master data is created correctly. No action Use APO transaction /SAPAPO/C3 (Application log) to find this message and find the user involved. Ensure that the user is using the latest GUI. If they are not request that the local helpdesk installs the latest GUI for the user. If they are using the latest GUI ask them to retry and it should work Use APO transaction /SAPAPO/C3 (Application log) to find this message and find the user involved. Ensure that the user is using the latest GUI. If they are not request that the local helpdesk installs the latest GUI for the user. If they are using the latest GUI ask them to retry and it should work

Use R/3 transaction ME23N to find the products involved in the purchase order. Within the purchase order use the menu path GOTO > VENDOR and the supplying plant will be in the SEARCH TERM 1/2 field. Ensure that the product is valid within this location within both R/3 and APO, if not, correct the master data and reprocess the queue. Try to create an identical order. If this works delete the initial order and delete the queue entry. Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run

Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Pre go". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "To be archived". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models Use APO transaction /SAPAPO/C3 (application log) to find this msg and search for the materials involved. The material has been given a plant specific material status of "Discontinued". Check to see if this should have been changed to "Active" by asking the MDR team. If this is a valid material for planning request that the MDR team changes the mm/pp status indicator for the material within the costing view to "Active". If this material should not be planned remove all occurrences of it within APO and any integration models

Use APO transaction /SAPAPO/C3 (application log) to find the material and location involved and then pass the msg text, material, location and system id to the FI-CO team. Reprocess the queue when they have corrected their data. Contact BASIS with the APO system name and ask them to check to see if LiveCache is running. If it is not it should be restarted. If ti is OK contact the GC DSP coordinator and ask for a livecache consistency check and delta report to be run Use APO transaction /SAPAPO/C3 (application log) to find the material, order and location involved. Re-explode the order and process the queue Reprocess the queue. If the lock persists request from GC DSP team member that a user session is terminated using SM04 Use APO transaction /SAPAPO/C3 (application log) to find the material and location involved. Verify that the vendor/material combination is valid and if it is request that the MDR team create the relevant MDR records for this combination. If this is not a valid combination remove all references to it in APO. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the order, material and location effected. Go to R/3 transaction C223 and search for all production versions for the material. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. If there are no production versions for the material, verify that this is a vlaid material for APO planning. If it is request that a master recipe, BOM and production version are made, included within an active integration model and then reprocess the queue. Due to the length of time that it takes for the master data to be created it would be worth removing all APO planned orders from the APO PPM, replanning on an alternative, valid PPM and making the invalid PPM inactive until the R/3 master data has been created correctly in APO.

Go to R/3 transaction C223 and search for all production versions for the material. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. If there are no production versions for the material, verify that this is a vlaid material for APO planning. If it is request that a master recipe, BOM and production version are made, included within an active integration model and then reprocess the queue. Due to the length of time that it takes for the master data to be created it would be worth removing all APO planned orders from the APO PPM, replanning on an alternative, valid PPM and making the invalid PPM inactive until the R/3 master data has been created correctly in APO. Use APO transaction /SAPAPO/C3 (application log) to find this message and find the order, material and location effected. Go to R/3 transaction C223 and search for all production versions for the material. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. If there are no production versions for the material, verify that this is a vlaid material for APO planning. If it is request that a master recipe, BOM and production version are made, included within an active integration model and then reprocess the queue. Due to the length of time that it takes for the master data to be created it would be worth removing all APO planned orders from the APO PPM, replanning on an alternative, valid PPM and making the invalid PPM inactive until the R/3 master data has been created correctly in APO. Go to R/3 transaction C223 and search for all production versions. If there are production versions but they are out of date range, locked, etc. correct what needs to be done, SAVE and use R/3 transaction CFP3 to send PPM changes to APO. Reprocess the queue. Contact BASIS and give them the message text and the system id If this is a validly planned material request the MDR team to complete the work scheduling view for tis material If this is a validly planned material request the MDR team to complete the work scheduling view for tis material Use APO transaction /SAPAPO/C3 (application log) to find this message and find the material effected. If this is a validly planned material request the MDR team to complete the work scheduling view for tis material

Use APO transaction /SAPAPO/C3 (application log) to find this message and find the user effected and the material and location effected. If the user validly requires access to the transaction request that they fill out a computer access form, get ti authorised by their manager and send it in to the helpdesk for the required transaction. If they do not require access to the transaction remove access to the related APO transactions such as all PP/DS planning screens

s all master data within the MDR for it. If this is not a valid APO planned material delete all references to it within APO.

tatuses are changed to allow planning. If this material should not be planned remove all occurrences of it within APO and any integration mo

o it within APO.

it within APO and any integration models

MSg # Msg text 150 ********** Delta Report Planned and Production Orders ***************

151 No active integration model for order &1 (material &2, plant &3) 152 153 154 155 156 157 158 159 160 161 162 163 164 Order &1 (material &2, plant &3) does not exist in SAP APO Order with internal number &1 (material &2, plant &3) only exists in APO Order with external number &1 (material &2, plant &3) only exists in APO Order &1 (material &2, plant &3) has different GUID Order &1 difference in number: &2 (APO) <-> &3 Order &1 difference in material: &2 (APO) <-> &3 Order &1 difference in plant: &2 (APO) <-> &3 Order &1 difference in total quantity: &2 (APO) <-> &3 Order &1 difference in open quantity: &2 (APO) <-> &3 Order &1 difference in end date: &2 (APO) <-> &3 Order &1 difference in ATP category: &2 (APO) <-> &3 Order &1 difference in item number: &2 (APO) <-> &3 Order with int. no. &1 (matl &2/plant &3) has conversion indicator in APO

165 166 167 168 169 170 180 181

Order with ext. no. &1 (matl &2/plant &3) has conversion indicator in APO Order with int. no. &1 (matl &2/plant &3, conv. ind.) already converted Converted order &1 (material &2, plant &3) does not exist in SAP APO Released order &1 has difference in total quantity: &2 (APO) <-> &3 Released order &1 has difference in open quantity: &2 (APO) <-> &3 Order &1 difference in release status ********** Delta Report External Procurement *************** Schedule line does not exist in SAP APO

182 Schedule line without external number does not exist in SAP R/3 183 184 185 186 187 188 189 190 191 210 211 212 213 214 215 216 Schedule line does not exist in SAP R/3 No active integration model exists in SAP R/3 GUID is different SAP APO product (&1) is not the same as SAP R/3 product (&2) SAP APO plant (&1) is not the same as SAP R/3 plant (&2) SAP APO quantity (&1) is not the same as SAP R/3 quantity (&2) APO requirements quantity (&1) is not the same as R/3 req. quantity (&2) SAP APO delivery date (&1) is not the same as SAP R/3 delivery date (&2) SAP APO number (&1) is not the same as SAP R/3 number (&2) Order &1: Difference in order GUID Order &1: Difference in order number (APO: &2 <-> R/3: &3) Order &1: Difference in item number (APO: &2 <-> R/3: &3) Order &1: Difference in schedule line number (APO: &2 <-> R/3: &3) Order &1: Difference in ATP category (APO: &2 <-> R/3: &3) Order &1: Difference in product (APO: &2 <-> R/3: &3) Order &1: Difference in location (APO: &2 <-> R/3: &3)

217 218 219 220 221 222 223 224 225 226

Order &1: Difference in sublocation (storage loc.) (APO: &2 <-> R/3: &3) Order &1: Difference in version (batch) (APO: &2 <-> R/3: &3) Order &1: Difference in material availability date (APO: &2 <-> R/3: &3) Order &1: Difference in requirement quantity (APO: &2 <-> R/3: &3) Order &1: Difference in confirmed quantity (APO: &2 <-> R/3: &3) Order &1: Difference in planned assignment quantity (APO: &2 <-> R/3: &3) Order &1: Difference in unit of measure (APO: &2 <-> R/3: &3) Order &1: Dif. in special stock (account assignment)(APO: &2 <-> R/3: &3) Order &1: Difference in special stock indicator (APO: &2 <-> R/3: &3) Order &1: Difference in schedule line GUID

235 Order &1 not in SAP R/3 (and faulty in SAP APO, VMI document) 236 Order &1 missing in SAP APO 237 Order &1 missing in SAP R/3 (VMI document) 238 239 310 311 312 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 ### Order &1 not in SAP R/3 (and errors in SAP APO) Order &1 is not contained in an active integration model SAP R/3 orders do not exist in SAP APO for material &1, location &2 SAP APO orders do not exist in SAP R3 for material &1, location &2 Different quantities &3/&4 for material/plant &1/&2 Shipment exists in OLTP, but not in SAP APO Shipment exists in SAP APO, but not in OLTP Rudimentary shipment: OLTP = & / APO = & Number of blocks for deliveries: OLTP = & / APO = & Number of blocks for deliveries to stages: OLTP = & / APO = & Number of blocks for stages: OLTP = & / APO = & Carrier: OLTP = & / APO = & Vehicle: OLTP = & / APO = & Data package too long to compare: OLTP = & / APO = & Delivery & assigned in OLTP shipment, but not in SAP APO shipment Delivery & assigned in SAP APO shipment, but not in OLTP shipment Delivery & for stage & assigned in OLTP shipment, but not in APO shipment Delivery & for stage & assigned in APO shipment, but not in OLTP shipment Stage & in OLTP shipment, but not in SAP APO shipment Stage & in SAP APO shipment, but not in OLTP shipment Start location type at stage &: OLTP = & / APO = & Start location at stage &: OLTP = & / APO = & End location at stage &: OLTP = & / APO = & End location at stage &: OLTP = & / APO = & Start time (UTC) at stage &: OLTP = & / APO = & End time (UTC) at stage &: OLTP = & / APO = & Check did not result in any errors Peg ID not in DM Stock

Action required Delete in APO if orders were created incorrectly Do not send if the product should be planned, correct the R/3 master data and reprocess the CIF queue errors Send to APO Delete in APO Send to APO

Send to APO

Do not send Do not send

Send to R/3 Send to APO

Send to APO Send to R/3 Delete in APO

Do not send

Do not send

Delete in APO Do not send Send to R/3 Delete in APO

Send to APO

Reason

Planned/production orders have not been included within an active integration model Check to see if there are any associated orders that are in APO and not in R/3 that need to be sent to R/3. Doing both of these actions will bring both systems in line.

Send to APO, the order without number will get R/3 number

Assume that R/3 is the master system so bring APO in line The order contains additional operation Signature which is not APO relevant hence end date is different, even after sending from R/3 the order remains in diffrence in content. Difference in the category of the orders

Conversion of planned order to process order has failed. Delete the CIF queue entries and use DELTA report to re-send the conversion indicator to R/3. If this is not possible delete the CIF queue entries and use /SAPAPO/RRP4, select the planned orders with conversion indicators and use the lightning icon to resend the message to R/3 Same for msg # 164 ????? Converted Planned order not available to APO

The order is found without external number I.e. the Purchase ordedr/requisition is in APO and not in R/3 ASN is created coming in APO as PO memo without deleting the PO in APO, IM0686114 is open to reolve this issue.

The delivery date 24:00:00 of previous day is not considered same as 00:00:00 next day, The GR, GI and transportation time not same in APO and R/3

The storage location for ZIMS type sales order is changed to IMSP. This appears in the difference, never transport.

Run RLCDELETE program for CU* once per week, The Delete in APO option does not delete the object in APO.

Only 'ZIMS' type sales orders are transferred to APO from R/3 system. Never transport other than ZIMS sales orders. Outbound deliveries created through Push despatch remain in the system, this should be deleted from APO

R/3 is the master system for stock so keep APO in line with R/3