Query:Convertion of PO to SO while inbound processing
Helo all,
I could successfully send PO data to receiver server using IDOC.
Now my requirement is creation of SO at runtime when PO enters in system as idoc.
I searched forums, but didnt got exact solution.
Kindly guide.
Thanks.
Edited by: Sanjay_lnt on Nov 12, 2010 3:03 PM
Hi Sanjay,
Do you want to create one SO along with PO in PO inbound FM ??? I think you are using the standard FM. So you can do the coding to create the SO from in the inbound FM exit or Badi. Better if can create one wrapper FM to create the SO and call that FM in background task, so that it will not hamper the inbound FM performance.
Also you can achieve the same functionality using output types. Just create one output types and attached with the EF in NACE and process it as special function.
Thanks
Subhankar
Similar Messages
-
Capture Messages while Inbound processing of IDOC
Hi ,
I have a scenario where in i have to upload a file from application server using inbound IDOC. I am using the program RSEINB00 (using submit) for this, The idoc is getting posted successfully but i need to capture the messages in form of a log so that i can find out what all IDOC numbers are generated and how many of them. In case any error is there. I need to display a log of it.
Timely help in this regard will be appreciated and rewarded suitably.
Rgds,
Kewal
P.S. : Please suggest if there is any other method to process inbound IDOC (accept we19 TX)Hi kewal ,
As per the scenario explained by you , I suggest you to do following steps
1.The program you are using is RSEINB00 , has a function mosule present named ' IDOC_ERROR_WORKFLOW_START'. This function module can gice yo the Error message log in case of Inboung IDOC processing fails.
2.You have two options , eithe you find out any user exit and atttach your own code to it or Complaetely cope that code into your z-program. Int he function module mentioned above , the export parameter ' G_MESSAGE_FIELDS ' wud give you the error message , error status , error no etc.
3. So for the INbound IDOC status messages starts with 51-70 , so depending upon ur logic , read all those message into an internal table .Then transfer that to a file .So an error log can be genearated.
I hope this solves ur problem.
Regards.
Note: Reward if useful. -
Error In inbound Processing IDoc
Dear All,
I am facing error while inbound processing of IDoc
In status record of IDoc following errors are occuring
Status 60 : EDI: Syntax error in IDoc (mandatory segment missing)
The segment E1MAKTM has the attribute 'Mandatory' in the syntax description of the basic type MATMAS05 (customer enhancement ). However, the segment is missing in the IDoc
Status 51: Application Document not posted
Log details :
Error : Material Number should be filled.
When i checked IDoc all 4 fields in E1MAKTM have the values in inbound IDoc.
Please guide me how to resolve these issues so that IDoc will be posted and Material Master will get created in reciever system.
ThanksHi Praveen,
I checked the data in IDoc for this segment.
It is ok as required in basic message type.
e.g. the error says that mandetory segment E1MAKTM is missing.
when i check basic type
MSGFN : Function
internal data type : CHAR
Internal length : 000003 characters
Position in segment : 001, Offset : 0063. external length : 000003
SPRAS : Language Key
internal data type : LANG
Internal length : 000001 characters
Position in segment : 002, Offset : 0066. external length : 000001
MAKTX : Material Description (Short Text)
internal data type : CHAR
Internal length : 000040 characters
Position in segment : 003, Offset : 0067. external length : 000040
SPRAS_ISO : Language according to ISO 639
internal data type : CHAR
Internal length : 000002 characters
Position in segment : 004, Offset : 0107. external length : 000002
is information.
and data in segment of IDoc is
MSGFN 005
SPRAS E
MAKTX MANATA2000 TEST ALE
SPRAS_ISO EN
which i think is ok.
I have no clue why this syntax error is coming.
Thanks
Niketan -
Error while creating inbound process code
Hi gurus,Iam creating a custom idoc.
800 -> sender
810 -> Receiver
i have completed outbound processing on 800.
On 810, completed following steps for inbound processing.
1.) I have added my Inbound FM in BD51.
2 ) Assigned my FM to Message type and Idoc type in WE57.
3 ) When adding my FM to process code in BD67, it is showing error that
Entry ZSATPC does not exist in TEDE2 - check your entry.
{ zsatpc is my custom process code }.
4) While Creating Process Code in WE42 with options [processing with ale service / Processing
by FM] and saving it is giving error that
" " is not a valid language.
And when I saw help (?) regarding this error, the following text appeared in a window.
Diagnosis
A key with language "" "" was specified for table "EDE2T". This is not a valid language.
This applies to field "LANGUA"
System Response
The system rejects the key.
Procedure
Enter a valid language. This is usually the language you logged on in.
You logged on in language "EN".
Table T002 contains a list of valid languages.
Please solve this error. Give me steps to create inbound process code.
thanx in advance. Hoping replies soon........
Satish.Dear Satish,
Very peculiar. The language should come from your log on language. Try to login into the system again. Call we42 again and see if it works.
Regards, Rakesh -
Error while Smart Sync inbound processing
Hi all,
I´m running MI 2.5 SP14 Patch 03.
My application works fine, but after synchronization I get the following message:
Exception while proccessing method SMARTSYNC : java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException : Error while Smart Sync inbound processing: java.lang.NullPointerException
The data are booked correctly, but the exception is thrown on the client. What´s wrong?
Thanks & regards,
BarbaraHi jo,
the whole trace file follows:
I ***** LOG / TRACE SWITCHED ON
I ***** Mobile Engine version: MI 25 SP 13 Patch 05 Build 200510140658
I ***** Current timezone: Europe/Berlin
I Trace severity: Info (70)
I Synchronize with backend called, Thread=Thread-33
I Thread=Thread-33 took lock for synchronization.
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429
I Skip performing Sync Event (0) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)
I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429
I AppLog severity: Warning (60)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463
I Saved Smart Sync outbound message for conversation id 4395713CB2A13B82E100000086F78463:
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI46414c5445524d4549455242
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId MI2853484152454429
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.core.RegistryInboundProcessingLog$RegistryInboundProcessingLogSyncEventListener on ConversationId MI2853484152454429
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956070B2A13B82E100000086F78463
I Saved Smart Sync outbound message for conversation id 43956070B2A13B82E100000086F78463:
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713DB2A13B82E100000086F78463
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.core.StatusUpdater for conversation id MI505545545a4b41554c / 43803A5EFBBB3102E100000086F78463 (User: PUETZKAUL, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802465AA13B82E100000086F78463
I Saved Smart Sync outbound message for conversation id 439802465AA13B82E100000086F78463:
I Saved Smart Sync outbound message for conversation id 439802465AA13B82E100000086F78463:
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B86D8D3B82E100000086F78463
I Saved Smart Sync outbound message for conversation id 439C13B86D8D3B82E100000086F78463:
I Skip performing Sync Event (0) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Outbound file size for user (SHARED) is 4311
I GzipDataCompression: Gzip data compression is switched on
I Inbound file size for user (SHARED) is 3114
I -
InboundContainer created: Type:R,Id:43A0856B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1
I -
InboundContainer created: Type:R,Id:43A0856B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1
I -
InboundContainer created: Type:R,Id:43A0856D99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3
I -
InboundContainer created: Type:R,Id:43A0856D99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3
I AlertInboundProcessor: Result 1 =
I AlertInboundProcessor: Result 2 =
I AlertInboundProcessor: Result 3 =
I -
InboundContainer created: Type:R,Id:43A0857099AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1
I -
InboundContainer created: Type:R,Id:43A0857099AE3B82E100000086F78463,SId:-1,Items:0,MaxI:1
I -
InboundContainer created: Type:R,Id:43A0857299AE3B82E100000086F78463,SId:-1,Items:0,MaxI:0
I Set last container id 0108331b71512ab15b57 for conversation id 43956070B2A13B82E100000086F78463
I Set last container id 0108331b72e737e90913 for conversation id 439C13B86D8D3B82E100000086F78463
I Set last container id 0108331b721c2005bfc3 for conversation id 439802465AA13B82E100000086F78463
I Set last container id 0108331b70094c518120 for conversation id 4395713CB2A13B82E100000086F78463
I Outbound file size for user FALTERMEIERB is 7536
I GzipDataCompression: Gzip data compression is switched on
I Inbound file size for user FALTERMEIERB is 9432
I -
InboundContainer created: Type:R,Id:43A0857F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:15
I -
InboundContainer created: Type:R,Id:43A0857F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:15
I -
InboundContainer created: Type:R,Id:43A0859199AE3B82E100000086F78463,SId:-1,Items:0,MaxI:2
W Request ID must have a length of 32 but it has a length of 20 Content: 0108331b71512ab15b57. Padding request id up with empty spaces.
I Processed Smart Sync inbound message for conversation id 43956070B2A13B82E100000086F78463
I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
successKeine Download-Daten aus R/3 im Downloader gefunden
I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
I Reset last container id for conversation id 43956070B2A13B82E100000086F78463
I -
InboundContainer created: Type:R,Id:43A0858699AE3B82E100000086F78463,SId:-1,Items:0,MaxI:2
W Request ID must have a length of 32 but it has a length of 20 Content: 0108331b70094c518120. Padding request id up with empty spaces.
I Processed Smart Sync inbound message for conversation id 4395713CB2A13B82E100000086F78463
I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
successKeine Download-Daten aus R/3 im Downloader gefunden
I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
I Reset last container id for conversation id 4395713CB2A13B82E100000086F78463
I -
InboundContainer created: Type:R,Id:43A0858B99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:5
E Error while Smart Sync inbound processing: java.lang.NullPointerException
java.lang.NullPointerException
at com.sap.ip.me.smartsync.syncIn.processors.InternalTopRowProcessor.assignStateIdWithWriter(InternalTopRowProcessor.java:413)
at com.sap.ip.me.smartsync.syncIn.processors.ProcessorTopSuccessReplace.startWithContainer(ProcessorTopSuccessReplace.java:81)
at com.sap.ip.me.smartsync.syncIn.processors.RowProcessorManager$RowProcessorDispatcher.start(RowProcessorManager.java:497)
at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor$3.startTop(SaxSyncInProcessor.java:515)
at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor$3.getNextHandler(SaxSyncInProcessor.java:437)
at com.sap.ip.me.xmlParser.MIXMLEventHandlerManager.startElement(MIXMLEventHandlerManager.java:80)
at com.sap.ip.me.xmlParser.MIXMLParser$ElementParser.parse(MIXMLParser.java:527)
at com.sap.ip.me.xmlParser.MIXMLParser.parse(MIXMLParser.java:164)
at com.sap.ip.me.smartsync.syncIn.SaxSyncInProcessor.processSyncInMessage(SaxSyncInProcessor.java:87)
at com.sap.ip.me.smartsync.syncIn.SyncInRuntimeImpl.processSyncInMessage(SyncInRuntimeImpl.java:250)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:344)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
I Processed Smart Sync inbound message for conversation id 439802465AA13B82E100000086F78463
I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
439802C55AA13B82E100000086F7846343A0858999AE3B82E100000086F78463successAlle Updates für einen TOP-Block erfolgreich (seqNo= 31, TOP Cntr=0000000001)000100012720053J 05 12
I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
E java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
at com.sap.ip.me.smartsync.syncIn.SyncInRuntimeImpl.processSyncInMessage(SyncInRuntimeImpl.java:284)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:344)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
E Error while Smart Sync inbound processing: Error while Smart Sync inbound processing: java.lang.NullPointerException. Reset Smart Sync data on device to ensure consitency with middleware.
java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:351)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
E Error while Smart Sync inbound processing: Error while Smart Sync inbound processing: java.lang.NullPointerException. Reset Smart Sync data on device to ensure consitency with middleware.
java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:351)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
W Exception while proccessing method SMARTSYNC
java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:368)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
E Exception while processing inbound container 43A0858B99AE3B82E100000086F78463
java.lang.RuntimeException: Error while Smart Sync inbound processing: java.lang.NullPointerException
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeImpl.process(SmartSyncRuntimeImpl.java:368)
at com.sap.ip.me.smartsync.core.SmartSyncRuntimeManager.process(SmartSyncRuntimeManager.java:214)
at com.sap.ip.me.smartsync.core.SyncAdapter.process(SyncAdapter.java:56)
at com.sap.ip.me.sync.SyncManagerImpl.processSingleContainer(SyncManagerImpl.java:160)
at com.sap.ip.me.sync.SyncManagerMerger.processInboundContainers(SyncManagerMerger.java:166)
at com.sap.ip.me.sync.SyncManagerImpl.processSyncCycle(SyncManagerImpl.java:709)
at com.sap.ip.me.sync.SyncManagerImpl.syncForUser(SyncManagerImpl.java:1142)
at com.sap.ip.me.sync.SyncManagerImpl.processSynchronization(SyncManagerImpl.java:774)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:402)
at com.sap.ip.me.sync.SyncManagerImpl.synchronizeWithBackend(SyncManagerImpl.java:285)
at com.sap.ip.me.api.sync.SyncManager.synchronizeWithBackend(SyncManager.java:79)
at com.sap.ip.me.apps.jsp.Home$SyncRunnable.run(Home.java:447)
at java.lang.Thread.run(Thread.java:534)
I -
InboundContainer created: Type:R,Id:43A0858F99AE3B82E100000086F78463,SId:-1,Items:0,MaxI:3
I Processed Smart Sync inbound message for conversation id 439802465AA13B82E100000086F78463
I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
43A0858D99AE3B82E100000086F78463000100012720053J 05 123J 05 12S
I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
I Reset last container id for conversation id 439802465AA13B82E100000086F78463
I -
InboundContainer created: Type:R,Id:43A0858499AE3B82E100000086F78463,SId:-1,Items:0,MaxI:4
I Processed Smart Sync inbound message for conversation id 439C13B86D8D3B82E100000086F78463
I Dumping file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
43A0858299AE3B82E100000086F784630001000095200500100010000952005001000000000000100601FLACHSTAHL 80 X 3 MM,DIN 10173J 05 0588.0000.000MFaltermeier
I End of content of file 'c:ProgrammeSAP Mobile InfrastructurelogsmartSyncInboundTmp.txt'
I Reset last container id for conversation id 439C13B86D8D3B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)
I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.core.StatusUpdater on ConversationId MI46414c5445524d4549455242
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.core.RegistryInboundProcessingLog$RegistryInboundProcessingLogSyncEventListener on ConversationId MI2853484152454429
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956070B2A13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713DB2A13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.core.StatusUpdater for conversation id MI505545545a4b41554c / 43803A5EFBBB3102E100000086F78463 (User: PUETZKAUL, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802465AA13B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B86D8D3B82E100000086F78463
I Skip performing Sync Event (10) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 43956071B2A13B82E100000086F78463
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.ccms.LastSuccessfulSyncAlert on ConversationId MI2853484152454429
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.services.os.AgentManager$AgentSyncEventListener on ConversationId MI2853484152454429
I Skip performing Sync Event (2) com.sap.ip.me.core.StatusUpdater for conversation id MI544553545f55534552 / 43A083B699AE3B82E100000086F78463 (User: TEST_USER, MSD: Name: / MOBILEENGINE_JSP (V. 250900), Target=, Type=com.sap.ip.me.core.FrameworkApplicationType)
I SyncEvent Performing com.sap.ip.me.ccms.AlertManagerImpl on ConversationId MI2853484152454429
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.sync.LogSender on ConversationId MI2853484152454429
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 4395713CB2A13B82E100000086F78463
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439802475AA13B82E100000086F78463
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I SyncEvent Performing com.sap.ip.me.smartsync.core.SyncAdapter on ConversationId 439C13B96D8D3B82E100000086F78463
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null)
I Skip performing Sync Event (2) com.sap.ip.me.smartsync.core.SyncAdapter for conversation id (null) -
Hi, getting Could not save the document to the repository for the following reason: [repo_proxy 30] DocumentFacade::uploadBlob - Query execute has failed : Error occurred while attempting to reconnect to CMS : Not a valid logon token. (FWB 00003) (hr=#0x80042a70) (WIS 30567) amongst lots of other errors when scheduling.
I was logged in as administrator and attempting to schedule a webi document to my self using the email option.
thanks in advanceHi Trinath,
Could you please confirm if you could save a new report as well or not; or is it specific to scheduling.
If you are unable to save a report also then I think this is due to the path of the Input File Repository Server or its temporary directory are not pointing to the same path, and their locations are set to 2 different hard drives
BOXI3.1 Server must use the same hard drive (local or network share) for the Input File Repository Server and its temporary directory.
- Shahnawaz -
System is not converting unit of measure ment while doing cost estimation.
Hi All,
System is not converting unit of measure ment while doing cost estimation.
Now i am explaining system setting. based on this kindly help me.
Our Base Unit of Measure Measuremnt in Material Master is M2 (meter square) and We have maintained Unit conversion in Master as 1 PC is <=>2.5 M2.
We are running costing for 1 M2.
Producion we are doing in Peaces (PC) . and i maintained Std Value for for Machin and Labour for PC only. and we maintained charge quantity in phases also.
While running cost estimation system is not converting std value of machin & labour into M2.instead it is showing full machin and labour time and value.
System showing PC value for M2 Cost estimate.
Can any one let me know where i am missing.
Thanks in Advance.
Regards,
SahilHi,
as per your explanation: 1 PC (piece) = 2,5 sqm (m2), standard values for "labour / machine" maintained per PC.
I guess within T-code CUNI, the unit PC does not allow any decimal places (means there can be only 1 piece, 2 pieces, 2 pieces but not 1 and a half pieces, 2,63 pieces,...)
Now if you are running plan cost estimate for quantity 1 sqm (m2) SAP picks the "labour / machine" values for 1 PC (and not for 1 / 2,5 = 0,4 pieces) as decimal places for unit pieces are not allowed so its up-rounding.
Run cost estimate for 10 sqm (m2) which should be 4 PC and the result should be fine.
Best regards, Christian -
Partner profile not maintained error while testing inbound processing
Hi gurus,
I am trying to upload a customer master data using LSMW idoc method, I followed all the required steps and then I tried to test the inbound processing using T.code we19 and there i gave my basic type as debcor01 and I clicked on standard inbound test but it gives me an error which says partner profile is not maintained, but I have maintained the partner profile and assigned the same in LSMW. So anyone of you can please help me to solve this problem.
thanks,
RajeevRajeev,
Check whether the Account Category is mantained properly or not.
K.Kiran. -
IDOC failure in R/3 Inbound processing
Hi
I was able to successfully generate XML files from Syndicator, but when it comes for processing in R/3 side it get fails all the time with the IDOC err msg : "IDoc included in IDoc packet containing an error: transfer it separate ".
Kindly adivce how to solve the same.
thanks in adv
AlexanderHi Ravi
Let me explain in detail.
From R/3 to MDM --> All materials in one XML file.
while from MDM to R/3 --> 3 diiferent IDOC am able to
see, one for each material in Inbound Processing.
kindly advice me how to fix the same.
thanks
Alexander -
Steps in Inbound Processing in ALE IDOC
Hi all,
Could anyone explain the steps to be followed in inbound processing in ALE Idoc.
I know we have to create a FM n then call that in a program. But still the detail steps are not clear.
An example will be really helpful.
ThanxHi
Outbound:
Step 1. Application document is created when transaction is saved.
2. Message control is invoked.
3. Messages are processed by system.
4. Messages are Edited (if desired).
5. Output (ALE / EDI) is checked
6. Validate against Message control record from Partner Profile
7. Application Document is saved.
8. Entry NAST table is created for every selected output program
along with Medium & Timing.
9. Check for Process Immediately .
If (yes)
Determine Processing Program from TNAPR Table.
ELSE
Execute RSNASTED Program.
10. Read Partner Profile to determine Process Code.
11. Process Code points to the Function Module & Invoked.
12. IDoc is generated.
13. Check for ALE Request.
if (Yes)
Perform Filters, Conversions, Version Changes etc.
Else.
IDoc is stored in DATABASE.
INBOUND:
Step 1. EDI Subsystem creates an IDoc file from EDI Messages
2. Subsystem calls Functional Module EDI_DATA_INCOMING from startRFC program.
3. Data in Control Record is validate against the Partner Profile.
4. IDoc is generated in Database and syntax check is carried out.
5. IDoc file is deleted once file read.
6. Event PROCESSSTATE REACHED is triggered in Idoc Object Workflow.
7. Check for Process Immediately.
If NO
Execute RBDAPP01 Program
Else
Read Process Code from Partner Profile
Process Code Points to Function Module
Application Document Posted.
further help:
check url
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/ale/configuration.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapdevelopment.co.uk/training
And also u can get lots of inof from the below link.
http://www.sapgenie.com/ale/why_ale.htm
Data Creation in Idoc
IDocs are text encoded documents with a rigid structure that are used to exchange data between R/3 and a foreign system. Instead of calling a program in the destination system directly, the data is first packed into an IDoc and then sent to the receiving system, where it is analyzed and properly processed. Therefore an IDoc data exchange is always an
asynchronous process. The significant difference between simple RFC-calls and IDoc data exchange is the fact, that every action performed on IDocs are protocolled by R/3 and IDocs can be reprocessed if an error occurred in one of the message steps.
While IDocs have to be understood as a data exchange protocol, EDI and ALE are typical use cases for IDocs. R/3 uses IDocs for both EDI and ALE to deliver data to the receiving system. ALE is basically the scheduling mechanism that defines when and between which partners and what kind of data will be exchanged on a regular or event triggered basis. Such a set-up is called an ALE-scenario.
IDoc is a intermediate document to exchange data between two SAP Systems.
*IDocs are structured ASCII files (or a virtual equivalent).
*Electronic Interchange Document
*They are the file format used by SAP R/3 to exchange data with foreign systems.
*Data Is transmitted in ASCII format, i.e. human readable form
*IDocs exchange messages
*IDocs are used like classical interface files
IDOC types are templates for specific message types depending on what is the business document, you want to exchange.
WE30 - you can create a IDOC type.
An IDOC with data, will have to be triggered by the application that is trying to send out the data.
FOr testing you can use WE19.
How to create idoc?
*WE30 - you can create a IDOC type
For more information in details on the same along with the examples can be viewed on:
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm#_Toc8400404
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a6620507d11d18ee90000e8366fc2/frameset.htm
http://www.sappoint.com/presentation.html
http://www.allsaplinks.com/idoc_search.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://www.erpgenie.com/sapedi/idoc_abap.htm
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30 )
Create Message Type ( WE81 )
Assign Idoc Type to Message Type ( WE82 )
Creating a Segment
Go to transaction code WE31
Enter the name for your segment type and click on the Create icon
Type the short text
Enter the variable names and data elements
Save it and go back
Go to Edit -> Set Release
Follow steps to create more number of segments
Create IDOC Type
Go to transaction code WE30
Enter the Object Name, select Basic type and click Create icon
Select the create new option and enter a description for your basic IDOC type and press enter
Select the IDOC Name and click Create icon
The system prompts us to enter a segment type and its attributes
Choose the appropriate values and press Enter
The system transfers the name of the segment type to the IDOC editor.
Follow these steps to add more number of segments to Parent or as Parent-child relation
Save it and go back
Go to Edit -> Set release
Create Message Type
Go to transaction code WE81
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter
Click New Entries to create new Message Type
Fill details
Save it and go back
Assign Message Type to IDoc Type
Go to transaction code WE82
Change the details from Display mode to Change mode
After selection, the system will give this message The table is cross-client (see Help for further info). Press Enter.
Click New Entries to create new Message Type.
Fill details
Save it and go back
Check these out..
Re: How to create IDOC
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
ALE/ IDOC
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
go trough these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
An IDoc is simply a data container that is used to exchange information between any two processes that can understand the syntax and semantics of the data...
1.IDOCs are stored in the database. In the SAP system, IDOCs are stored in database tables.
2.IDOCs are independent of the sending and receiving systems.
3.IDOCs are independent of the direction of data exchange.
The two available process for IDOCs are
Outbound Process
Inbound Process
AND There are basically two types of IDOCs.
Basic IDOCs
Basic IDOC type defines the structure and format of the business document that is to be exchanged between two systems.
Extended IDOCs
Extending the functionality by adding more segments to existing Basic IDOCs.
To Create Idoc we need to follow these steps:
Create Segment ( WE31)
Create Idoc Type ( WE30)
Create Message Type ( WE81)
Assign Idoc Type to Message Type ( WE82)
imp links
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapedi/idoc_abap.htm
www.sappoint.com
--here u can find the ppts and basic seetings for ALE
http://sappoint.com/presentation.html
www.sapgenie.com
http://www.sapgenie.com/ale/index.htm
Check these links.
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://www.sapgenie.com/sapedi/idoc_abap.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/0b/2a60bb507d11d18ee90000e8366fc2/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/78/217da751ce11d189570000e829fbbd/frameset.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sappoint.com/abap.html
http://help.sap.com/saphelp_erp2004/helpdata/en/dc/6b835943d711d1893e0000e8323c4f/content.htm
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.doc
http://edocs.bea.com/elink/adapter/r3/userhtm/ale.htm#1008419
http://www.netweaverguru.com/EDI/HTML/IDocBook.htm
http://www.sapgenie.com/sapedi/index.htm
http://www.allsaplinks.com/idoc_sample.html
http://www.sapgenie.com/sapgenie/docs/ale_scenario_development_procedure.docs
Please check this PDF documents for ALE and IDoc.
http://www.sappoint.com/abap/ale.pdf
http://www.sappoint.com/abap/ale2.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEIO/BCMIDALEIO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCMIDALEPRO/BCMIDALEPRO.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CABFAALEQS/CABFAALEQS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDISC/CAEDISCAP_STC.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVEDI/CAEDI.pdf
Check below link. It will give the step by step procedure for IDOC creation.
http://www.supinfo-projects.com/cn/2005/idocs_en/2/
Reward points for useful Answers
Regards
Anji -
I create an outbpund idoc as a file on a file port : FILEIN.
FILEIN port is defined as a file port with Dir parameter set as : /tmp/
and FM parameter set as : EDI_PATH_CREATE_DATE_TIME . No parameters are maintained for Inbound file .
I create outbound idoc with :
Reciever Port FILEIN and Sender port A00001 (defined as a trfc port ).
The Idocs are generated in the specified directory .
Now i want to process these idocs with RSEINB00 Program .
I give the filename and Port name : FILEIN to the program .
The partner profile is maintained for the inbound processing .
But I somehow recieve the error : '56 : Reciever port in control record is invalid. '
How can this be solved ? DO i need to maintain the Inbound file parameters too in the File port . ?Hi,
You should first turn your output IDoc file to an Inbound IDoc file. use the transaction code we12 to that.
Following is the more info on Using We12.
We12 - IDoc testing tool which will emulate an EDI subsystem, by taking a outbound text file IDoc previously generated by SAP and use it to create and process an inbound IDoc. It is also possible to create an outbound IDoc from an inbound IDoc as well. Commonly referred to as the Turn-around program
Field level documentation on each field on the We12 screen..
Source:
Directory + file: The field contains the path and filename of the existing IDoc text file at the operating system level.
Target:
Directory + file: the target fields contain the path and filename of the IDoc text file that is to be created. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (see WE46 for IDoc Administration; WE 21 for Port Definition).
Sender:
Partner Number: Customer or Vendor number of the sender - when testing inbound messages, this partner number must exist as a valid inbound partner (transaction WE20).
Partner Type: Code, which identifies the type of sender (i.e. LI Vendor; KU Customer).
Partn.function: Code, which identifies role of the partner (i.e. SH Ship-to).
Message type: Code, which identifies the type of data, based on the EDI message type (i.e. ORDERS, INVOIC).
Variant: Code, which further subdivides the type of message (i.e. MM or FI for a logical message type of INVOIC).
Function: Code, which defines the function of the message with regard to its transmission.
Test: Flag indicating that this is a test message. This is one of the keys to finding the inbound partner profile.
Port: Logical ID of the sending system. Enter the logical name of the receiving as defined in the transaction WE21. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).
Recipient:
Partner Number: Customer or Vendor number of the receiver.
Partner Type: Code, which identifies the type of receiver (i.e. LI - Vendor; KU - Customer).
Partn.function: Code, which identifies role of the partner (i.e. SH - Ship-to).
Direction: The direction that the newly created IDoc will be assuming -1 for outbound, 2 for inbound. Default is 2.
Client: The client that the newly created IDoc will be processed in. The default is the client that the user is logged into when executing this transaction.
Port: Logical ID of the receiving system. Enter the logical name of the receiving system in the form 'SAPxxx'. 'xxx' stands for the ID of the SAP System. The default entries of these fields are based on the definition of the TESTPORT specified in the IDoc Administration transaction (WE46).
Turn-around program examples: When taking an outbound purchase order IDoc (which was generated via MM purchase order create) and turning it around to test inbound SD sales order creation via EDI, the Sender would be a customer while the Receiver would be a vendor. If using an outbound advanced ship notice IDoc (generated via SD delivery processing) and turning it around to test inbound shipping notification, the Sender would be a vendor, and the Receiver would be a customer. If using an outbound invoice IDoc (generated via SD invoicing) and turning it around to test inbound EDI invoice processing, the Sender would be a vendor, and the Receiver
Hope this helps.
Mark the Helpful answerers..
Regards,
Nagaraju Chidurupalli -
Inbound processing is not happening for XMG integration
Currently our project deals with B2B and XMG integration
We are able to send outbound messages to B2B from XMG successfully.
For Inbound messages
1. B2B is picking up payload
2. Identifying Agreement
3. Decrypting and verifies digital signature
but could not deliver the message to ECX_INQUEUE
Log
====
2008.02.06 at 07:04:32:292: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression Enter
2008.02.06 at 07:04:32:293: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression idexp = /*[local-name()='envelope']/*[local-name()='itemSyncResponse']
2008.02.06 at 07:04:32:293: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:getIdentificationExpression Exit
2008.02.06 at 07:04:32:307: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.document.custom.CustomDocumentPlugin:processIncomingDocument Exit
2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:XXX: processIncomingMessage setting seq numbers
2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:processIncomingMessage Call Incoming Request Processor
2008.02.06 at 07:04:32:308: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Enter
2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest TransportBindings created
2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:incomingRequest Create a Message Table Row for Request message with message state Continue Processing
2008.02.06 at 07:04:32:309: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow Enter
2008.02.06 at 07:04:32:312: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:312: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryExchangeProtocolRevision
2008.02.06 at 07:04:32:316: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryExchangeProtocolRevision
2008.02.06 at 07:04:32:316: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:317: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryDocumentProtocolRevision
2008.02.06 at 07:04:32:319: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryDocumentProtocolRevision
2008.02.06 at 07:04:32:322: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:322: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
2008.02.06 at 07:04:32:327: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
2008.02.06 at 07:04:32:333: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty name Oracle Development
2008.02.06 at 07:04:32:333: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:insertMsgTblRow toparty type and value AS2 Identifier0060974050142
2008.02.06 at 07:04:32:334: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:334: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: queryTradingPartnerIdentificationType
2008.02.06 at 07:04:32:336: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: queryTradingPartnerIdentificationType
2008.02.06 at 07:04:32:337: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:364: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createBusinessMessageReceiverInter
2008.02.06 at 07:04:32:367: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createBusinessMessageReceiverInter
2008.02.06 at 07:04:32:367: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateNativeEvtTblRow Enter
2008.02.06 at 07:04:32:373: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:374: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: createDataStorage
2008.02.06 at 07:04:32:377: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: createDataStorage
2008.02.06 at 07:04:32:381: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:updateNativeEvtTblRow msgInfo.id = <[email protected]_te>
2008.02.06 at 07:04:32:382: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:
** DbAccess:updateNativeEvtTblRow:tip_wireMsg protocolCollabID = null
2008.02.06 at 07:04:32:383: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:383: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateWireMessage
2008.02.06 at 07:04:32:387: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateWireMessage
2008.02.06 at 07:04:32:387: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.Request:continueRequest Collaboration Control not required ..continuing Request processing
2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination Enter
2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to destination. protocol is XMLGateway Queues
2008.02.06 at 07:04:32:388: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:deliverMessageToDestination deliver message to XMLGW2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 Converting B2B message to ECX message..
2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 Inbound - B2BtoECX - Enter
2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 B2B Message -2008.02.06 at 07:04:32:389: Thread-10: B2B - (DEBUG) : COLLABORATION_NAME : null2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : ACTION_NAME : M4U_SRC_ITEM_SYNC_RESP
2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : DOCUMENT_TYPE : M4U_SRC_ITEM_SYNC_RESP
2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : DOCUMENT_TYPE_REVISION : 1.0
2008.02.06 at 07:04:32:390: Thread-10: B2B - (DEBUG) : SOURCE_NAME : 1Sync-AS2
2008.02.06 at 07:04:32:391: Thread-10: B2B - (DEBUG) : DESTINATION_NAME : Oracle Development
2008.02.06 at 07:04:32:392: Thread-10: B2B - (DEBUG) : PAYLOAD : <Payload Goes Here>
2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) : Wed Feb 06 07:04:32 PST 2008 ECX Message -
2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry Could not deliver the message; exception message is null2008.02.06 at 07:04:32:393: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.MessageHandler:handleAppMessageRetry No application side retry
2008.02.06 at 07:04:32:617: Thread-10: B2B - (ERROR) Error -: AIP-50903: Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero
at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:325)
at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:275)
at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:589)
at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:428)
at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:357)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1693)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2007)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1939)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1897)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:595)
2008.02.06 at 07:04:32:618: Thread-10: B2B - (ERROR) Error -: AIP-50903: Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero
at oracle.tip.adapter.b2b.msgproc.MessageHandler.handleAppMessageRetry(MessageHandler.java:325)
at oracle.tip.adapter.b2b.msgproc.MessageHandler.deliverMessageToDestination(MessageHandler.java:275)
at oracle.tip.adapter.b2b.msgproc.Request.putMsg(Request.java:589)
at oracle.tip.adapter.b2b.msgproc.Request.continueRequest(Request.java:428)
at oracle.tip.adapter.b2b.msgproc.Request.incomingRequest(Request.java:357)
at oracle.tip.adapter.b2b.engine.Engine.processIncomingMessage(Engine.java:1693)
at oracle.tip.adapter.b2b.engine.Engine.incomingContinueProcess(Engine.java:2007)
at oracle.tip.adapter.b2b.engine.Engine.handleMessageEvent(Engine.java:1939)
at oracle.tip.adapter.b2b.engine.Engine.processEvents(Engine.java:1897)
at oracle.tip.adapter.b2b.data.MsgListener.onMessage(MsgListener.java:463)
at oracle.tip.adapter.b2b.data.MsgListener.run(MsgListener.java:335)
at java.lang.Thread.run(Thread.java:595)
2008.02.06 at 07:04:32:621: Thread-10: BusinessLogicLayer - (DEBUG) Authorization disabled. UserBootstrapped:false, useAuthorization:true, configType:Runtime
2008.02.06 at 07:04:32:621: Thread-10: BusinessLogicLayer - (DEBUG) Push Stack: updateBusinessMessage
2008.02.06 at 07:04:32:626: Thread-10: BusinessLogicLayer - (DEBUG) Pop Stack: updateBusinessMessage
2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.msgproc.DbAccess:DbAccess:updateMsgError(3 params) Exit
2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) oracle.tip.adapter.b2b.engine.Engine:notifyApp retry value <= 0, so sending exception to IP_IN_QUEUE
2008.02.06 at 07:04:32:627: Thread-10: B2B - (DEBUG) Engine:notifyApp Enter
2008.02.06 at 07:04:32:630: Thread-10: B2B - (DEBUG) notifyApp:notifyApp Enqueue the ip exception message:
<Exception xmlns="http://integration.oracle.com/B2B/Exception" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<correlationId>null</correlationId>
<b2bMessageId>8C57CE13117EF46D5340000013A02150-1</b2bMessageId>
<errorCode>AIP-50903</errorCode>
<errorText>Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero</errorText>
<errorDescription>
<![CDATA[Machine Info: (ap6003idmz.us.oracle.com)^M
Message "8C57CE13117EF46D5340000013A02150-1" retry count is zero ]]>
</errorDescription>
<errorSeverity>2</errorSeverity>
</Exception>
Following doc - protocol parameters are set for failed message
=================================================
Identification Expression (XPath) for XML Document : /*[local-name()='envelope']/*[local-name()='itemSyncResponse']
Document Routing ID : b2buser1
Inbound Process Type : M4U_SRC
Inbound Process Subtype : ITEM_SYNC_RESPONSE
Outbound Process Type : M4U_SRC
Outbound Process Subtype : ITEM_SYNC_RESPONSE
Inbound Party Code : Internal
DTD/XSD Namespace Conversion :NONE
Please advise us.
Thanks
PraveenHello,
Plese make sure that the ECX queues are present and are appropriately refferred from the Delivery Channel in B2B UI. I will request one of my team memeber to work with you if the issue still persists.
Rgds,Ramesh -
RFC_ERROR_SYSTEM_FAILURE during inbound processing
Hi,
I am getting below error while using startrfc for inbound processing.
RFC Call/Exception: SYSTEM_FAILURE
Group Error group 104
Key RFC_ERROR_SYSTEM_FAILURE
Message Port 'SAPCC4' does not exist in the table of port descriptions
I already have port SAPCC4 defined in my SAP system.
Please help.
Thanks & Regards,HI ,
go to Idoc -number which is error generated..
see the control record..in EDIDC table..
see the Partner and go to we20 and see the partner and open inbound and see the message and open
details..
see whether the same port assigned to the Message type or ,,,if not assign..
if the port is TCP/IP or R/3 connection..go to t-code sm58 and see the error details for the RFC
destination assigned in the port..
Prabhudas -
LSMW idoc Inbound Processing settings
Hi,
We have done LSMW with BAPI method to create Bank master.
In Idoc Inbound Processing settings -
We created partner type as 'B' i.e, for BANK
While creating Partner Number it is not allowing to create Partner Number. The error is "Enter a permissible partner number"
Please let me know what would be the problem.
Regards,
Hari
Edited by: Bhatlapenumarthy Hari Krishna on Sep 12, 2008 9:31 AMHi,
Use patner type as US only and LSMW as Patner number.
this will surely solve your problem .
plz do this way :
The first requirement is a file port for the file transfer. If required, create a port of the file type via Maintain ports. To do this, position the cursor on "File" and press Create. You should be in change mode. SAP recommends:
Port: LSMW
Name: Legacy System Migration Workbench
Version: 3 (IDoc record types SAP Release 4.x)
Outbound file Please enter a (dummy) physical directory and a file name, i.e. u2018filelsmwu2019 ·
As an addition, you can specify a tRFC port. This port is required, if you do not want to create a file during data conversion but submit the data in packages directly to function module IDoc_Inbound_Asynchronous.
SAP recommends:
Port: assigned by the system
Version: 3 (IDoc record types SAP Release 4.x)
RFC destination: Name of R/3 System
Name of port: Legacy System Migration Workbench.
Then the partner type should be defined or selected. SAP recommends:
Partner type: "US" (User)
As of release 4.5A, this partner type is available in the standard system. Up to release 4.0B inclusive, this partner type is not available in the standard program and should be added. SAP recommends:
Partner type: Create US
Report name: /SAPDMC/SAP_LSMW_PARTNERTYPES
Form routine: READ_USER
Short description: any.
Finally a partner number should be defined or selected. SAP recommends:
Partner number: LSMW
Partner type: US
Partner status: A (active)
Type: US
Language: DE or EN
Person in charge: Your user ID.
Activate IDoc inbound processing
reference : help.sap
thanx.
Edited by: Dhanashri Pawar on Sep 12, 2008 7:10 AM -
IDoc Inbound Processing for CREMDM & DEBMDM
Hi experts,
I'd like to gather some feedback from you regarding the topic ERP IDoc Inbound Processing for CREMDM & DEBMDM. As you all know, there's currently no option to directly process CREMDM/DEBMDM IDocs in ERP. Currently you have to use PI for splitting the CREMDM/DEBMDM message into its related ADRMAS and CREMAS/DEBMAS IDocs.
My areas of interest are:
1) How satisfied are you with the current situation? Does the split work? Are there issues or problems in the current message handling? What are the Pro's and Con's from your point of view?
2) What would be the requirements for a CREMDM/DEBMDM handler? What would you expect? Maybe you have implemented something similar on project basis and could post some feedback?
One painpoint I'd see with a CREMDM/DEBMDM inbound is that you'll lose the IDoc Monitoring capabilities. The message split allows a single record tracing in the IDoc Monitor (as there is a 1:1 relation between IDocs and records). This changes for the mass processing. The monitor would display only the status of the IDoc and you'd need some other monitoring capabilities to check the results on record level. What are your thoughts about that? Is the monitoring important? Would the application log be a feasible solution for that challenge?
Additional comments are welcome, of course.
Best regards
Michael
PS: @ Matt, please contact me by mail. thanks.Hello ,
Here are some other pain areas regarding the message split :
1. Complicated monitoring proess & reprocessing error idocs : We have to monitor ADRMAS & CREMAS or ADRMAS & DEBMAS during inbound processing. Also we could not find any best practices to reprocess error idocs. E.g. If ADRMAS fails & CREMAS succeeds what is the impact . Also the impact if it is reveresed. We know for sure that if CREMAS fails , vendor will not be created / updated. But we could not find specific pointers for ADRMAS failures.
2. It is a tedious process to link CREMAS with corresponding ADRMAS idoc specially when SAP maintains internal number range for vendors.
3 . The process is complicated if you are managing customer or vendor contact information with contact address . We could succesfully implement the integration but it took us a while to reach end-point.
4. Splitting really does not seem to support if ERP maintains internal number range.
5. Another major issue we observed is , if ADRMAS is under process & corresponding DEBMAS or CREMAS is posted , it fails raising the message that Account is locked. Default serialization does work in ERP system . But overlap of few microseconds also cause this error.
Hope this helps !!
Please let me know if you need any other specific details since we have used MDM - ECC integration using PI to its maximum extent .
Regards
Yogesh
Maybe you are looking for
-
Where are my iTunes libraries?
I have an iPod Touch and my new iPad Mini. On my iPod Touch, all of the music and video files are available from the iTunes desktop, or by navigating to (User)/iTunes/iTunes Library. However, even though I back up my iPad Mini and have lots of music
-
JTable Blank Rows When INSERT/DELETE in other panel with same ViewObject
Hi, Jdev 10.1.2 JClient 2 panels based on same ViewObject in same AM One panel with Grid UI => JTable Other panel with Form UI When I insert or delete a record in the panel with Form UI and return to the panel with JTable blank rows are displayed. Th
-
Photos just imported are modified (Reveal in Finder) (9.2.2)
Hi, i'm a french iPhoto user, I found a problem since the 9.2.2 update. When importing photo from any camera (iPhone 4S, Sony A700 or Canon 600D) in iPhoto, the option "Reveal in Finder" shows me "Modified" or "Original" but photos are just imported
-
I'm using a networked linksys NSLU to house my music library and music files. When I plug in my iPod (video), it starts to synch immediately (I have it set to do this). The problem I see is that it takes forever >10 minutes to just even evaluate my 1
-
Positions under Organizational Units.
Dear All, I need to maintain a Ceiling for Organizational Units with respect to Positions. For example : There is a Org Unit - HR Dept , and it has a restricition of 25 positions. So when i try to create a 26th position under this Org Unit ,it should