Global ATP in multiple SCM Systems

Hi Experts
Has anybody seen a situation where a single ECC system does a GATP check in two different SCM systems. I understand that it is not uncommon to have one ECC system integrated with two or more SCM systems for different modules (one for DP, one for SNC, one for GATP, etc).
But we have a situation where we are replacing an existing GATP implementation with a new one (in a different SCM server). Business would like to do a pilot of the new implementation functionality from a risk perspective (scope limited to one plant in distribution network). During the short interim of the pilot, we could have a situation where one sales order could do a GATP in the 'old' server and another order does GATP in the 'new' server. At any time a single order is sourced from one plant, so at the minimum an entire order is availability checked in either of the two systems.
I believe that using the CIF ATP integration model, we can control which logical system the GATP check is done in. We will test this in a sandbox environment, but would like to know your thoughts. Appreciate any concerns/ watch-outs.
Rishi Menon

Hello Rishi,
It is quite possible to connect more than one SCM system to ECC technically. Business case will be little specific to customer requirements i.e having existing SCM systems for different business units.
GATP check can be carried out in different SCM system as you rightly mentioned based on CIF integration model. It doesn't create any issue. We have similar system set-up for internal use.
Only issue what I see here is, in case of RBATP, if you are using cross location ATP check, if will not give you desired results. Second issue will be for planned supply components, if material is planned in separate SCM system.
Such system set-up works fine when you are having isolated materials and location to plan and GATP.
Regards,
Dinesh Goyal

Similar Messages

Two SCM Systems connected to one ERP System

Hello Experts,
Here again I got a doubt.
Is it technically possible to connect two SCM Systems via CIF to one ERP System?
Because I heard that we could connect more than one ERP System to one SCM System, but not vice versa.
If you have seen a system in production like this, what are the pros and cons of having such a scenario?
Expecting your valuable replies!
Thanks and Best Regards,
Suresh

Hi,
technically it's no problem to connect two or more SCM systems to the same ERP system. We have one for DP/ PP/DS, one for EWM and one for SNC connected to the same R/3 systems. You however might get problems with the bom explosion for planned orders being sent from SCM to R/3.
The bom explosion uses field MARC-APOKZ which is maintained automatically by CIF. If there are multiple SCM system using CIF for product master data the field might not be set up correctly and the bom explosion could be wrong.
As a solution SAP provided OSS note 1576703.
Regards.
Hubert

ATP Check(in SCM ) for a Configurable product during sales order creation.

HI Guru's,
our client is implementing GATP(SCM) and Variant Config(ECC 6.0)
when a Sales order is created for a Configurable Product of 20" width and 10" diameter, and with some other Characteristics, He wants the ATP check to be done for that particular product with specific width and diameter.
Is there any possible solution?
Plz let me know....
Thanks
jk

Hi
Assuming that you know how to configure Variant configuration in R/3, ATP check in R/3 I will list down the ATP set up and setup relevant to Variant Configuration in SCM.
APO side.
1.Check Definition of Characteristics and Class system:
SAP APO - Implementation Guide -> SAP Advanced Planner and Optimizer (SAP APO) -> Basis Settings -> Define Class System (CDP or Classical Characteristics)
2. Check Mode ( use same requirements class used in R/3 mat master)
SAP APO - Implementation Guide -> SAP Advanced Planner and Optimizer (SAP APO) -> Global Available-to-Promise (Global ATP Check) -> General Settings -> Maintain Check Mode
3. Create a check instruction with your check mode and AE(make to stock SD order) combination and set up the desired ATP check method in it.
SAP APO - Implementation Guide -> SAP Advanced Planner and Optimizer (SAP APO) -> Global Available-to-Promise (Global ATP Check) -> General Settings -> Maintain Check Instructions
4. Check Control with your ATP group and AE business event.
SAP APO - Implementation Guide -> SAP Advanced Planner and Optimizer (SAP APO) -> Global Available-to-Promise (Global ATP Check) -> Product Availability Check -> Maintain Check Control
5.Maintain suitable scheduling horizon in SAP APO - Implementation Guide -> SAP Advanced Planner and Optimizer (SAP APO) -> Supply Chain Planning -> Production Planning and Detailed Scheduling (PP/DS) -> Global Settings -> Maintain Global Parameters and Defaults -> Planning Tab
5. Don't forget to CIF classes and charecteristics
6. Maintain check mode, ATP group, PP/DS horizon, planning procedure 3 in product master.
If you want to trigger production you have to maintain planning procedure 5 in product master and appropriate settings for MATP like configure check instructions, production type Mutli level ATP. you have to have valid BOM and Routings, CIF PDS for the material, maintain production version in material master, etc. That will be quite a complex scenario again.
This should give you proper results. Hope this helps.
regards
Mohan V R chunchu
Edited by: Mohan V R Chunchu on Jan 30, 2008 6:17 AM

Remove unnecessary SD orders in SCM system

Hello,
To remove unnecessary Sales Orders regularly in SCM system I found out a program "/SAPAPO/SDORDER_DEL ". But I am unable to figure out the parameters to be used once I execute this program. Can someone please let me know, if there is a document which explains the fields in the tab of the program /SAPAPO/SDORDER_DEL :
1. Delete on database
2. Delete in SAP livecache and in Database
3. Delete All DB Sales order data
Suggestions are much appreciated.
Thanks

HI,
This is the Program Documentation available in system
Short text
ATP: Delete (SD) Orders From Database
Purpose
You use this report to delete the SD sales document data from the database. Normally, the order data remains in the database (it is not deleted as in liveCache).
In order to limit the data volume, you should schedule the report to delete the orders, if necessary, and it should be dependent on the lifetime of your orders.
Example
For example, a sales order is completed in six weeks. Such a sales order would be archived in SAP R/3 but such an archiving concept does not exist in SAP APO. You use this report to remove the sales order from the database.
Integration
A location product or a location can only be deleted if SD sales documents for this location product no longer exist in the database (that is, if, for example, no more entries exist in the tables /SAPAPO/ORDADM_I or /SAPAPO/ORDPART).
Features
A check is normally carried out before an order is deleted to see if this order still exists in liveCache. If this is the case, the order is not deleted.
You can also print out a list of the orders that cannot be deleted if you have set the relevant indicator.
In exceptional cases, you can deactivate this check and nevertheless still delete the selected orders.
If you have set the Delete all orders indicator, the order data from the database is completely deleted without any check. You should take great care when using this function.
Note
If you have deleted orders that are still being used for business purposes, you must start a new initial data supply or, if you know the orders, you must perform a further ATP check to transfer the data from SAP R/3 to SAP APO.

Multiple SAP systems in MSCS with Oracle

Hello,
We are going to install a BI instance in a MSCS cluster in which there is already a SAP system installed and clustered.
The SO is Windows 2008 and Oracle 10.2.0.4.
My problem is about the Oracle sw. In previous SAP releases there was a guide called "Installation of Multiple SAP systems in MSCS: Oracle".
For my release Netweaver 7.0. EHP1 SR1, there is no specific guide. All the references are the installation guide and part related to MSCS installation and a white paper about "new configuration of multiple SAP systems with Windows 2008 Failover Clustering".
In all that documents I haven't found what to do with the database. In the beginning of the installation documents says that Multiple Oracle_home for different database instances are not supported in an MSCS configuration. But in the pages related to the MSCS installation says "if required, set up multiple Oracle Homes".
So, what's the option? Multiple Oracle_homes or MCOD? Be in mind that I already have a SAP system in this cluster, so I already have an Oracle home c:\oracle\<SID>\102
Have you work in this scenario?
Thanks and best regards,
Ana.

Hi,
Officially SAP does not support Multiple SAP Systems in One MCSC Cluster. If such installation & configuration has been done by SAP Global Technology Partner then and then only SAP provide support.
what's the option? Multiple Oracle_homes or MCOD?
GO for multiple oracle_home , in which the same drive letter for oracle_home should be used on local disks in both MCSC cluster nodes. And the same oracle_home should be junctioned to the shared location on shared space.
The Chapter 7 High Availability with Microsoft Cluster Service of [Inst. Guide SAP NetWeaver 7.0 incl. EHP1 SR1|http://service.sap.com/~form/sapnet?_SHORTKEY=01100035870000659894&_OBJECT=011000358700000353072009E] contains all the required information with detail. Refer it.
Regards,
Bhavik G. Shroff

Urgent: Error in Inbound Proxy in SCM system

Hi All
Please give your inputs to solve following problem I am facing. I am working on XI first time so please help me out to solve the following problem. Please let me know if you need any more info.
Thanks a lot for your help guys.
I am sending ORDERS.ORDER05 from R/3(ECC6.0) to SCM (5.0) through XI. I am using standard message interface ReplenishmentOrderNotification_In to send data to ICH configured on SAP SCM System.
I am using XI adapter at receiver end. My message successfully going to SCM. SXMB_MONI, its giving error. After clicking on error flag it displays a table with 3 entries, please find them below.
1. Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202027) 032(/SCMB/ORDER)
2. TST 20080429202851 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
3. Partner key(s) not found 042(/SCMB/MDL_BASIC)
Please find the XML message from ERROR node from Inbound Proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="ABAP">APPLICATION_ERROR</SAP:Code>
<SAP:P1 />
<SAP:P2 />
<SAP:P3 />
<SAP:P4 />
<SAP:AdditionalText />
<SAP:ApplicationFaultMessage namespace="http://sap.com/xi/SCMBasis/Global">ReplenishmentOrderNotificationFault</SAP:ApplicationFaultMessage>
<SAP:Stack>Application has thrown an exception</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
Please find contents of Trace XML message from Inbound proxy
<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
- 
- <SAP:Trace xmlns:SAP="http://sap.com/xi/XI/Message/30">
<Trace level="1" type="B" name="CL_XMS_HTTP_HANDLER-HANDLE_REQUEST" />
- 
<Trace level="1" type="T">XMB was called with URL /sap/xi/engine/?type=receiver</Trace>
<Trace level="1" type="T">COMMIT is done by XMB !</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-ENTER_XMS" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-SET_START_PIPELINE" />
- 
<Trace level="1" type="B" name="SXMBCONF-SXMB_GET_XMB_USE" />
<Trace level="1" type="B" name="CL_XMS_TROUBLESHOOT-ENTER_PLSRV" />
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">XMB entry processing</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T01:31:18Z CET</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">* *</Trace>
<Trace level="1" type="T">****************************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_UC_EXECUTE" />
- 
<Trace level="1" type="T">Message-GUID = 48165647672B03B5E10080000A0C640C</Trace>
<Trace level="1" type="T">PLNAME = RECEIVER</Trace>
<Trace level="1" type="T">QOS = EO</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_ASYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline = RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Get definition of internal pipeline = SAP_RECEIVER</Trace>
<Trace level="1" type="T">Queue name : XBTR0003</Trace>
<Trace level="1" type="T">Generated prefixed queue name = XBTR0003</Trace>
<Trace level="1" type="T">Schedule message in qRFC environment</Trace>
<Trace level="1" type="T">Setup qRFC Scheduler OK!</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Going to persist message</Trace>
<Trace level="1" type="T">NOTE: The following trace entries are always lacking</Trace>
<Trace level="1" type="T">- Exit WRITE_MESSAGE_TO_PERSIST</Trace>
<Trace level="1" type="T">- Exit CALL_PIPELINE_ASYNC</Trace>
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="T">--start sender interface action determination</Trace>
<Trace level="1" type="T">select interface *</Trace>
<Trace level="1" type="T">select interface namespace</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--start receiver interface action determination</Trace>
<Trace level="1" type="T">Loop 0000000001</Trace>
<Trace level="1" type="T">select interface ReplenishmentOrderNotification_In*</Trace>
<Trace level="1" type="T">select interface namespace http://sap.com/xi/SCMBasis/Global</Trace>
<Trace level="1" type="T">no interface found</Trace>
<Trace level="1" type="T">--no sender or receiver interface definition found</Trace>
<Trace level="1" type="T">Hence set action to DEL</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T16:19:34Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 000</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-04-30T20:52:28Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 002</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:34:19Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 004</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:35:19Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 006</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = RAJARANGA</Trace>
<Trace level="1" type="Timestamp">2008-04-30T22:41:24Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 008</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:07:18Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 010</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:30:07Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 012</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T00:53:39Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-RESTART_ERROR_MESSAGE" />
- 
<Trace level="1" type="T">Persisting message with status ManualRestart, version: 014</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="T">* Setup of qRFC Scheduler OK!!!</Trace>
<Trace level="1" type="T">***************************************</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
<Trace level="1" type="B" name="CL_XMS_MAIN-PERSIST_READ_MESSAGE" />
<Trace level="1" type="T">Note: the following trace entry is written delayed (after read from persist)</Trace>
<Trace level="1" type="B" name="SXMS_ASYNC_EXEC" />
- 
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="T">Starting async processing with pipeline RECEIVER</Trace>
<Trace level="1" type="T">system-ID = SCS</Trace>
<Trace level="1" type="T">client = 001</Trace>
<Trace level="1" type="T">language = E</Trace>
<Trace level="1" type="T">user = AMOL</Trace>
<Trace level="1" type="Timestamp">2008-05-01T01:04:22Z CET</Trace>
<Trace level="1" type="T">-----------------------------------------------------</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PIPELINE_SYNC" />
- 
<Trace level="1" type="T">Get definition of external pipeline RECEIVER</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-LOOKUP_INTERNAL_PL_ID" />
<Trace level="1" type="T">Corresponding internal pipeline SAP_RECEIVER</Trace>
<Trace level="1" type="B" name="PLSRV_CALL_INBOUND_PROXY" />
- 
- <Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV">
<Trace level="1" type="B" name="CL_XMS_MAIN-CALL_PLSRV_LOCAL" />
- 
<Trace level="1" type="B" name="Inbound Framework" />
</Trace>
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="T">Application Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="T">System Error at Receiver... => ROLLBACK WORK</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST" />
<Trace level="1" type="System_Error">Application-Error exception return from pipeline processing!</Trace>
<Trace level="1" type="B" name="CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST" />
- 
</SAP:Trace>
Regards
Amol

Hi All
Thanks for your inputs, we are a step ahead now. We applied few notes I will be posting details soon. At the moment we stuck at one poin, its giving a configuration related error. Please find the process log from SXMB_MONI from SCM system. It is saying Buyer missing in fact we have configured BP01 in SCM system and same we are getting from ECC system.
Hope to hear from you soon. Thanks a lot for your inputs.
ReplenishmentOrderNotificationFault
Proxy Class (Generated)
Detailed Information
Start of inbound processing: ReplenishmentOrderNotification (ID 0000000000202043) 032(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'BEFORE_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
TST 20080508141414 (type MessageCreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_PARTYID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
Start generic process type determination 000(/SCMB/BIF_CU)
Process type could not be determined - search for standard process type 002(/SCMB/BIF_CU)
Standard process type (ICH) determined successfully 013(/SCMB/BIF_CU)
Start action determination for addresses 070(/SCMB/BIF_CU)
No Customizing found; standard action is 'map all addresses' 072(/SCMB/BIF_CU)
End of action determination for addresses 071(/SCMB/BIF_CU)
Start partner role determination 060(/SCMB/BIF_CU)
Partner role is 'buyer (sold-to party)' 063(/SCMB/BIF_CU)
Partner role determination completed successfully 061(/SCMB/BIF_CU)
TST 20080508000000 (type CreationDateTime) was transferred as local time, interpretation as UTC 022(/SCMB/BIF_MI)
The active implementation of BAdI '/SCMB/BIF_MI_ITMBPRT' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
The active implementation of BAdI '/SCMB/BIF_MI_PRODID' 'BEFORE_MASTER_DATA_ACCESS' has been run 080(/SCMB/BIF_COMMON)
TST 20081027000000 (type DeliveryPeriodStartDateTime, item 00010, sched. line 1) is local, interpret. as UTC 024(/SCMB/BIF_MI)
Order 4500000105 item 00010: 'DeliveryPeriodEndDateTime' missing in schedule line 1 090(/SCMB/ORDER)
The active implementation of BAdI '/SCMB/BIF_I_REPLORD' 'AFTER_CONVERSION' has been run 080(/SCMB/BIF_COMMON)
BOL processing started for object /SCA/CL_SVORDER process name REPLORDER 006(/SCMB/DM_BOL)
Start: read ODM order 250(/SCMB/ORDER)
End: read ODM order 251(/SCMB/ORDER)
Start: validation framework 254(/SCMB/ORDER)
Validation started for validation profile POC1 (ICH - REPLORDER - HEADER) 606(/SCMB/DM_BOL)
Business partner 'buyer' is missing in order 4500000105 021(/SCMB/ORDER)
Validation for val. prof. POC1 (ICH, REPLORDER, HEADER) ended with errors and warnings 608(/SCMB/DM_BOL)
End: validation framework 255(/SCMB/ORDER)
Start alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 504(/SCMB/ANOT)
End of alert notification for application ALEN - time 08.05.2008 19:15:18 - process mode F 525(/SCMB/ANOT)
Start: write ODM order 252(/SCMB/ORDER)
End: write ODM order 253(/SCMB/ORDER)
BOL processing ended for object /SCA/CL_SVORDER process name REPLORDER 007(/SCMB/DM_BOL)
End inb. proc.: ReplenishmentOrderNotification (ReplenishmentOrder ID ) 033(/SCMB/ORDER)

Error during System copy of SCM system

*Hi
We are performing system copy of SCM system. The Java was not at all running in the system now while performinfg system copy we are facing following errror.*
ERROR 2009-10-23 12:05:39.123
CJS-30071 Execution of UTL tool 'C:\j2sdk1.4.2_12-x64\bin\java.exe -classpath E:\usr\sap\SD2\SYS\global\sltools\sharedlib\launcher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain
MB1ES1018/sapmnt/SD2/SYS/global/security/lib/tools/iaik_jce.jar;
MB1ES1018/sapmnt/SD2/SYS/global/security/lib/tools/iaik_jsse.jar;
MB1ES1018/sapmnt/SD2/SYS/global/security/lib/tools/iaik_smime.jar;
MB1ES1018/sapmnt/SD2/SYS/global/security/lib/tools/iaik_ssl.jar;
MB1ES1018/sapmnt/SD2/SYS/global/security/lib/tools/w3c_http.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/sap.comsl.ut.infoprovider_lib.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/sap.comsl.ut.manager.offline.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/antlr.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/exception.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/jddi.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/logging.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/offlineconfiguration.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/opensqlsta.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/sap.comtcsdtcvlimpl.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/SDMutil.jar;E:/usr/sap/SD2/SYS/global/sltools/sharedlib/SLUtil.jar;E:\usr\sap\SD2\DVEBMGS00\exe\ojdbc14.jar -export -type=keydb "-expfile=C:/Program Files/sapinst_instdir/SCM51/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP/PREEXP/usages_data.xml" -log=UTL_load_usages.log -sid=SD2 -dsn=jdbc/pool/SD2 -ssprops=E:/usr/sap/SD2/SYS/global/security/data/SecStore.properties -ssk=E:/usr/sap/SD2/SYS/global/security/data/SecStore.key' aborts with return code 64 due to a database connection error. DIAGNOSIS: The connection parameters are wrong or the database server has been shut down. SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/SCM51/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP/PREEXP/UTL.java.log' for more information.

Hi.
>SOLUTION: Check 'UTL_load_usages.log' and 'C:/Program Files/sapinst_instdir/SCM51/LM/COPY/ORA/EXP/CENTRAL/AS-ABAP
>/PREEXP/UTL.java.log'
Hi,
Could you please paste above logs here and also check whether database is up or not...
Thanks
Sunny

Error during System Copy in SCM system

*Hi
We are performing System Copy of SCM system. Java was not running in the system from the starting. we are facing following error while performing system copy* Please Help..
Oct 23, 2009 12:05:38... Info   : Successfully parsed!
Oct 23, 2009 12:05:38... Info   : Executing command Export...
Oct 23, 2009 12:05:38... Info   : Establishing DB connection...
Oct 23, 2009 12:05:39... Path   : Exception : The DataBase is down or the connection parameters are wrong: -sid=SD2 -dsn=jdbc/pool/SD2 -ssprops=E:/usr/sap/SD2/SYS/global/security/data/SecStore.properties -ssk=E:/usr/sap/SD2/SYS/global/security/data/SecStore.key -keyphrase=null
java.lang.Exception
     at com.sap.exception.BaseExceptionInfo.traceAutomatically(BaseExceptionInfo.java:1141)
     at com.sap.exception.BaseExceptionInfo.<init>(BaseExceptionInfo.java:413)
     at com.sap.exception.BaseException.<init>(BaseException.java:302)
     at com.sap.sl.ut.infoprovider.exceptions.UTInfoException.<init>(UTInfoException.java:96)
     at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:215)
     at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:624)
     at com.sap.sl.ut.manager.command.Export.executeExportKDB(Export.java:56)
     at com.sap.sl.ut.manager.command.Export.execute(Export.java:80)
     at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
     at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
     at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Caused by: java.sql.SQLException: ORA-01017: invalid username/password; logon denied
     at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:283)
     at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:278)
     at oracle.jdbc.driver.T4CTTIoauthenticate.receiveOauth(T4CTTIoauthenticate.java:790)
     at oracle.jdbc.driver.T4CConnection.logon(T4CConnection.java:362)
     at oracle.jdbc.driver.PhysicalConnection.<init>(PhysicalConnection.java:420)
     at oracle.jdbc.driver.T4CConnection.<init>(T4CConnection.java:165)
     at oracle.jdbc.driver.T4CDriverExtension.getConnection(T4CDriverExtension.java:35)
     at oracle.jdbc.driver.OracleDriver.connect(OracleDriver.java:801)
     at com.sap.sql.jdbc.NativeConnectionFactory.createNativeConnection(NativeConnectionFactory.java:215)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.createConnection(OpenSQLDataSourceImpl.java:522)
     at com.sap.sql.connect.OpenSQLDataSourceImpl.getConnection(OpenSQLDataSourceImpl.java:276)
     at com.sap.sl.ut.manager.persistence.db.DBConnection.connectViaSecureStore(DBConnection.java:159)
     at com.sap.sl.ut.manager.persistence.db.DBConnection.connect(DBConnection.java:171)
     at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.connect(DataBaseInfoFactory.java:213)
     at com.sap.sl.ut.manager.persistence.db.DataBaseInfoFactory.constructSystemInfo(DataBaseInfoFactory.java:624)
     at com.sap.sl.ut.manager.command.Export.executeExportKDB(Export.java:56)
     at com.sap.sl.ut.manager.command.Export.execute(Export.java:80)
     at com.sap.sl.ut.manager.command.Command.exec(Command.java:88)
     at com.sap.sl.ut.manager.UtlMain.exec(UtlMain.java:60)
     at com.sap.sl.ut.manager.UtlMain.main(UtlMain.java:56)
     at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
     at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
     at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
     at java.lang.reflect.Method.invoke(Method.java:324)
     at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Oct 23, 2009 12:05:39... Info   : Severe (database) error. Return code: 64

> We are performing System Copy of SCM system.
How did you do the system copy? Did you use sapinst and export the Java content?
Markus

Integrating SAP-ERP system to SAP-SCM system via SAP-XI

Hi All,
My requirement is to make a scenario for Integrating SAP-ERP system to SAP-SCM system via SAP-XI,Sender side is IDOC Adapter and Receiver side is Proxy.As iam not aware of the scenario procedure can any body could explain briefly step-by-step on this.
Thanks in Advance.
ram

Hi,
Sender is IDOC so no need to take any communication channel & sender agreement in ID window.
Find below link of more information on IDOC configuration
Introduction to IDoc-XI-File scenario and complete walk through for starters.
Troubleshooting File-to-IDOC Scenario in XI.
Convert any flat file to any Idoc-Java Mapping
IDOCs (Multiple Types) Collection in BPM
Outbound Idoc's - Work around using "Party"?
Troubleshooting File-to-IDOC Scenario in XI.
Proxy Configuration
File to R/3 via ABAP Proxy

Multiple SAP systems in a MSCS

can someone tell me that he/she installed multiple SAP systems in a MSCS environment?
DB:ms sqlserver 2005
OS:windows server 2003 enterprise edition cluster
sap: ecc 6.0 and BW

HI,
yes, is possible as of 700 systems.
you have to do it with your SAP Global Technology Partner, document "Installation of Multiple SAP Systems in MSCS: MS SQL Server" (Oracle etc) is available on
https://service.sap.com/instguides
-> SAP NetWeaver 7.0 (2004s)
-> Installation
-> 2 - Installation - SAP NetWeaver Systems
Best regards

Multiple SCM(s) one R3

Hello Experts,
We have a scenario where we have 2 SCM systems connected to one R3 system. One of the SCM systems is used for DP, SNP, and PP/DS. I will refer to this as the planning SCM. The other SCM is used for GATP. All of our planned orders are created in and converted to process orders in the planning SCM system. Our planners maintain all of their resource down times, and relevant shifts in this planning SCM as well. The resources and PPMs exist in the GATP SCM system, but they are only there to allow the process orders to be created. The process orders need to exist in the GATP SCM because, we promise to these process orders on the GATP check. From what I can tell, this set up has caused us 2 problems on the GATP side that I am hoping someone can help me with.
When the planned orders are converted to process orders the dates match between ECC and the planning SCM system. In the GATP SCM system, the dates do not match. I am nearly positive this is because the GATP system is rescheduling the order based on its version of the truth, which has infinitely planned resources and no resource downtimes. Is there a way to stop our GATP SCM system from re-planning the process orders that are sent from ECC? We would like these process orders to inherit whatever dates are sent from R3, which ultimately came from our planning SCM system. We thought a user exit on the inbound SCM side might work, but we were hoping there was another setting somewhere. Does anybody know of a setting or how the user exit would need to work?
When scheduling changes happen to the process orders on the planning SCM side, the dates are updated in ECC, but no transfer is triggered to send the updates to the GATP SCM system. I believe this may be because the update was caused by one SCM system, so the system is not smart enough to know that it has to update the other SCM system. Does anyone know of a good way to get the transfer events to trigger to the GATP SCM system from these types of process order updates? I know I can do a re-initial transfer every night, but I would like to avoid this option of possible.
Thanks,
Matthew Bruckner

MB,
Well, I have never heard (until now) anyone using a distribution key for output, except in repetitive scenarios. I learn something new every day!
If this is the case, I can only make suggestions, since I have no system similar to yours to model a solution.
I would look at ways to avoid use of any scheduling Strategy profile. I have never tried this, but investigate removing the R/3 interface default strategy profile (IMG>APO>Supply Chain Planning>PP/DS>Global Settings>Maintain Global Parameters)
I would look at different production versions, one for 'Planning SCM' and one for 'GATP SCM'. This might help if your date problems are being caused by GATP system being forced to do forward scheduling.
I would look at ways to avoid/prevent any scheduling heuristics from being run in GATP. Likewise avoid any planning heuristics. Perhaps consider a custom PP Planning procedure. I don't know how this would affect your distribution key requirements.
Or, maybe try using a Strategy profile that only permits backward scheduling, combined with a PPM with negligible process time.. You would have to have this profile not exit upon scheduling errors.
I still think, though, that the best solution is 'one SCM'.
Perhaps one of the other forum members will offer a suggestion.
Best Regards & good luck,
DB49

Global ATP with product allocations and SD returns

Dear all,
We have been setting up an implementation scenario with an ECC 6.0 and SCM 5.0 system which verifies SD orders versus SCM product allocations.
With SD orders and SD contracts everything works fine. But we have a problem with using SD returns (same material and plant used like the SD orders): We would expect the system also to check the returns for product allocation quantities but it seems that the SCM availability check does not enter the product allocation procedure at all (we have some user-exits in use but these are only accessed when we go via SD orders, no access at all for SD returns).
Is there any special setting which we have to activate in order to have the SD returns properly processed with product allocations? (Customizing "Set the Transfer of Returns to SAP APO" within ECC is activated) The system somewhere gets stuck during the check within the SCM system.
Thanks for providing assistance regarding this matter.
Kind regards,
Klemens

Hi folks, did you resolve your issue here? I assume what you are wanting is for the Returns order to free up allocations qtys that had previously been consumed by the originating sales order, that is, incoming orders qty should be reduced by the amount of the returns order. I know that when a sales order line item is rejected the incoming order qty is reduced, but I'm not sure it is possible for a returns order to do this.
ATP Man, are you saying that as category BZ is not supported by Allocations that it is therefore not possible for the Incoming Orders Qty to be reduced by a Returns Order? I have a business reequirement to do exactly that.
If it is not possible to do this through the automatically via the ATP check, the only way I can think to address this, would be to try and transfer the Returns qty to SCM after the order is saved and then to have a macro that reads the returns qty and reduces the Incoming Orders qty by the qty of the return.
Paul.

Possibility of connecting multiple BW systems to single ECC system

Hi all,
I have a requirement in my company to connect multiple BW systems to single ECC system. Would like to confirm whether this may not be supported by all BW extractors in particular the delta mechanism?
For logistics extractor in ECC side in RSA7 it stores BW System as target which shows they support multiple BW systems as target, but for FI extractors which keeps delta timestamps in BWOM2_TIMEST table, it doesn't store the target system. I'm afraid if we connect multiple BW systems to single ECC system, some of the delta records might go to one BW system and some others go to the other BW system when we execute delta load in both BW systems.
Thank you very much in advance.
regards,
arie

Hi,
You can very well connect multiple BW systems to single ECC system and you will not miss any delta as well. In the source system for each delta data source a delta queue is maintained for each target system.
for e.g. I have two BW systems ABW and BBW connected to AEC system then for 0FI_AP_4 data source we will have DQ1_ABW and DQ2_BBW as two different delta queues (I am not following any naming conventions, actual names will be as per the target system logical name).
The settings maintained in BWOM2_TIMEST table are across the system and they define some global settings e.g. till what time the FI data should be extracted in BW system, for e.g. the time maintained is 2.00 AM then though you do extraction from multiple systems same data will be extracted till next time interval occurs.
In summery you can very well connect multiple BW systems to a single ECC system.
Regards,
Durgesh.

SCM question -2 SCM system connected to single R/3 system

Hi Gurus,
What is the implication using two SCM systems with single R/3 system when both SCM systems using for different modules (say one for DP and other one for GATP).
I know SAP recommends using multiple OLTP with single SCM. But this scenario opposit of that.
Thanks,
BKN
Edited by: BKN on May 6, 2008 7:08 PM

It is possible that there can be multiple SRM system connected to 1 R/3 system...You need to setup on...IMG>SRM->SRM Server->Technical Basic Settings>Define Backend System-> There you need to provide Logical System/Description/RFC Distination and Sys Type.
I hope it clarifies your issue.

GLOBAL ATP WITHOUT APO

When I was at Sapphire in 2007, SAP demo'd a global ATP from within SD that utilized enhancement pack 1 or 2. Now I need to implement something like this, without using APO. However, I can't find any references to in through Enhancement Pack 3 (our current version). Has anyone seen this done? Basically, if a customer orders an item, then we want to check two distribution centers, then look at stores with either high avaialability/overstock or near-by. Thanks in advance for ideas. I just need leads not a detailed solution.

Christophe
The end objective of GATP is the same as that of regular ECC ATP - provide customers with committed dates and quantities. Having said that, GATP provides a HUUUGE improvement in functionality compared to the ECC ATP check - for example, rules based ATP check for product/ location substitution, multi-level ATP check, capable-to promise, etc.
Because of these dramatic improvements in functionality, GATP has the potential to do a lot more than order promising - depending on the business requirement, it can reduce inventory, improve customer service, improve fill rates, ....
GATP is executed in the APO system and is a module of APO. Best place to start with documentation is SAP help.
Rishi Menon

Global ATP in multiple SCM Systems

Similar Messages

Maybe you are looking for