on 03-21-2015 5:32 AM
Hi Everyone,
I'm trying to transfer a router from ME 15.03 to ECC 6.06 with the system rule "Enable Replication of ME Routing to ERP" set to "Yes with Change Management" but I'm getting an error.
In the queue monitor I get the following message:
[STEP = STD_END]. BAPI call failed! MES routing 7000?TEST_ROUTER?1?1 could not be converted (see log)
In the netweaver log I get the following fatal error (two appear):
[Transaction: 78] UserEvent : <?xml version="1.0" encoding="UTF-8"?><CO_MES_ECN_MAINTAIN>
<INPUT>
<CHANGE_HEADER>
<CHANGE_NO/>
<STATUS>01</STATUS>
<AUTH_GROUP/>
<VALID_FROM>20150320</VALID_FROM>
<DESCRIPT>test router</DESCRIPT>
<REASON_CHG/>
<DELETION_MARK/>
<INDATE_RULE/>
<OUTDATE_RULE/>
<FUNCTION/>
<CHANGE_LEADER/>
<EFFECTIVITY_TYPE/>
<OVERRIDING_MARK/>
<RANK/>
<RELEASE_KEY/>
<STATUS_PROFILE/>
<TECH_REL/>
<BASIC_CHANGE/>
</CHANGE_HEADER>
<MES_ROUTINGID>7000?TEST_ROUTER?1?1</MES_ROUTINGID>
<OBJECT_TLIST_N>
<ACTIVE>X</ACTIVE>
<LOCKED/>
<OBJ_REQU/>
<MGTREC_GEN/>
<GEN_NEW/>
<GEN_DIALOG/>
</OBJECT_TLIST_N>
</INPUT>
<TABLES>
<DETAIL_RETURN>
<item>
<TYPE/>
<ID/>
<NUMBER/>
<MESSAGE/>
<LOG_NO/>
<LOG_MSG_NO/>
<MESSAGE_V1/>
<MESSAGE_V2/>
<MESSAGE_V3/>
<MESSAGE_V4/>
</item>
</DETAIL_RETURN>
</TABLES>
</CO_MES_ECN_MAINTAIN>
Hide Full Message
Severity: Fatal
Date: 2015-03-20
Time: 20:14:02:051
Category: /Applications/XMII/Xacute/Event
Location: com.sap.xmii.bls.executables.actions.logging.LoggingActions
Application: sap.com/xapps~xmii~ear
Thread: Thread[Managed_Application_Thread_63,5,Managed_Application_Thread]
Data Source: j2ee\cluster\server0\log\applications_00.log
Arguments:
Passport User Activity ID: fa0ca238ce2d11e482d700000096d0ca
Message ID:
Session: 0
Transaction:
User: MESYS
Time Zone:0-400
Customer Message Component:
Runtime Component: sap.com/xapps~xmii~ear
Correlation ID: 9883850000025748
Passport Session: FA0CA238CE2D11E482D700000096D0CA
Passport Connection: 00000000000000000000000000000000
Passport Connection Counter: 0
Log ID: C000AC15151923710000000000000F14
Host: CHA-SP09-QV
System: MEQ
Instance: J00
Node: server0
I checked in ECC and a change note was created but the tasks weren't.
If I change the system rule to "Yes" the routers transfer without any problems.
Does anyone have any ideas of what can be wrong??
Thanks in advance for any help.
Kevin
Hello Kevin,
I know over an year has passed but I was wondering, have you got a resolution for that problem? I'm facing the exact same thing but it is with ME 15.1.1.
If you could please share your resolution it would be highly appreciated.
Many thanks,
Ricardo
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Sergiy,
Thank you for your reply.
After debugging the PRE-XSLT transaction
Visiprise/ERPShopFloorIntegration/workflow/Routing/GenerateChangeNumber, I was able to find the function CO_MES_ECN_MAINTAIN in our ECC is different than what is expected in ME.
I found out the reason on SAP Note 2005268 - Error handling when creating change numbers.
We currently have our SAP_APPL component on SP SAPKH61702 and I'm hoping to get this issue fixed once we apply the recommended SP.
As a general comment for our community here, that transaction Visiprise/ERPShopFloorIntegration/workflow/Routing/GenerateChangeNumber logs a Fatal Error message on Netweaver for the Request.xml and one for the Response.xml of that function CO_MES_ECN_MAINTAIN call regardless its execution status which could be very confusing for who is troubleshooting routingExportRequest message. It might be worth it a little customization there to avoid those "errors" to be logged.
Thanks,
Ricardo
Hi,
I think the best way to figure this out is to submit a ticket to PP-SFC component. If required, they will forward it to ME component for further investigation with their comments.
Regards,
Konstantin Chernega
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
7 | |
6 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.