MATMAS outboud Idoc: problem in SM58

Hi experts,
i have done Idoc to File scenario through SAP PI 7.0 server,
here SAP ECC 6.0 is the sender (MATMAS05- idoc) and Fileserver is the Receiver system and the SAP PI 7.0 is the Middleware system.
created Prtner profiles, customer distribution model view and distributed.
i triggered the IDOC from SAP ECC 6.0 system, (BD10), in WE05it is showing as IDoc processing success, data has sent to port and the status code is 03.
then i checked in tcode SM58, there it is showing under the
user - username
Function Module - IDOC_INBOUND_ASYNCHRONOUS
Target System - PI7CLNT001
Status Text - : : 000
can anybody tell me what would be the problem?
Thanks,
Kumar

Hi,
what kind of connection do you use between ECC and PI - RFC / Proxy? You can check this via SM59.
Is the file reaching PI or does the IDoc stuck in SM58? If it stucks in SM58 - try to reprocess it (hit F6 button).
Also what settings do you use in WE20 for partner PI7CLNT001?
Thanks,
Kai

Similar Messages

Idoc problem while loading

Hi Gurus,
I am getting error "Idocs missing: No end-confirmation arrived in the Warehouse from" while loading data from R3 to BW via process chain.
Can any one please suggest me how solve this problem.
Thanks in advance.
Regards
Tony

Hi,
It may be due to below reasons...
1. Check whether the Log Table is full in the BW side.
2. Check Whether the Connection to Source System is fine.
3. System might be busy , Many jobs running in system.
Go to SM58 in BW system , find TRFC queue with enteries for each LUW . U can come to know why IDOC is not processed by looking at the error there . Also check whether the job is finished successfully in Source System. U can process the LUW in Sm58 manually from Edit menu entry ....
Thanks
DSt

ALE IDOC Problem...

HI..
I am facing a problem on the inbound side.
If I check the IDoc in WE02, I am getting a status error as
"No status record was passed to ALE by the a"
Customised IDoc is used.
Please advise if you can Thnx

HI,
IAM GIVING A DOCUMENT WHICH HELPS YOU TO UNDERSTAND EASILY AND YOURSELF CAN WORKOUT WITH THIS REAL TIME SCENARIO WHICH TRANSFERS THE DATA BETWEEN TWO SYSTEMS.
Application Linking and Enabling (ALE)
In this document you will learn the step-by-step procedure to setup the ALE system and go through a transaction between two clients
For our purpose we have two clients
namely Client 100 and Client 200.
System name is SAPKDC (FOR BOTH 100 AND 200 CLIENTS).
Distribution of Material Master Data Between two Systems
1) SETUP LOGICAL SYSTEM: (Note: Do Not Create This Step)
To do this follow the following steps
Execute SALE Transaction Code
On The Screen Click on Sending and Receiving Systems.
Then Click on Logical Systems.
Then Click Defining Logical Systems.
Click New Entries Button
(E.g. (LG100 sending system)
(LG200 receiving system))
Enter two logical system names and their description.
Save
Comeback to SALE Transaction Code screen.
2) Now you have to allocate the created logical systems to respective clients.( Note: Do Not Create This Step)
LG100 assign to client 100
LG200 assign to client 200
To do this, do the following.
Click Assigning Client to Logical System.
Ignore the message that comes up on the screen.
Select client 100
Click details button on the toolbar icon or press F2.
In the logical system box, enter LG100.
Click on the save Icon
Click the back button.
Now select client 200.
Click details icon or press f2.
In logical Systems box, enter LG200.
Save
Back.
Comeback to SALE Transaction Code screen.
3) Maintain RFC Destination: (TR.CODE:SM59)
(Note: Do Not Create This Step)
Click Create Button on the Screen
On the Screen Maintain RFC Destination i.e LG200.
Enter LG200 in RFC destination box.
Connection type is 3
Give a description for the RFC destination.
Maintain Technical Settings on Details on Technical Settings tab
Target Host as : SAPKDC (NOTE: Save it as a Host Name)
Maintain Logon Details on Logon/Security tab.
Language: EN.
User:      MMUSER200 (This is the logon for dist.)
Client :      200
Password:      MM1234.
Save.
Click on create to do the above process for Client 200 in
The client 200 system.
4) Maintain Distribution Model.(BD64). (ABAPer role starts here)
Execute Maintain distribution model directly for
creating the model.
Click on change mode button on App tool bar of the Screen.
Create Model View pushbutton on App tool bar of the Screen.
A pop screen will appear in which you specify
Short text as Distribution for MM Data.
Enter Technical Name as LGMODEL.
Select Model View and Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG100.
Receiver as      LG200.
Again Click on Add Message Type Pushbutton on App toolbar of the Screen.
A popup screen will appear in which you specify
Model View as      LGMODEL.
Sender as           LG200.
Receiver as      LG100.
SAVE.
On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Logical System as LG200.
Then execute the screen.
Click back.
Again On the same screen goto Menubar and select EDIT.
Again select Model View and then select Distribute.
****LOGIN to client 200.
Execute Tr.code BD64 and again On the same screen goto Menubar and select Environment.
And then select Generate Partner Profiles , then execute it.
On the Screen specify the Model View as LGMODEL
And Specify the Logical System as LG100.
Then execute the screen.
Click back.
*******Switch back to client 100 Session.
5) Create Material using MM03 Tr.Code.
Enter the material name as LGMATERIAL
Industry sector as      Mechanical Engineering
Material Type as           Finished Products.
And then Click on Data Pushbutton on the App tool bar.
Select views.
In the select views box for materials check basic data 1 AND 2.
Click enter icon.
In the next screen that you get
Give the text of the material as NEW MATERIAL.
Base unit of measure as KG.
Gross Weight as 200.
Net Weight as 100.
Weight Unit as KG.
In the description area language (E) and material description.
Click Save.
Now I Created a Material in Client 100 , I want to transfer this data to Client 200.
6) Execute BD10 to transfer the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client100).
Then a Screen will be displayed in which it shows that
1 Master Idoc Generated .. Enter
1 Communication Idoc Generated..Enter.
*******LOGIN to Client 200.
7) Execute BD11 to get the material in which you specify
the material as LGMATERIAL and
message type as MATMAS (client200).
8) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
If not follow these steps.
9) Execute Tr.code WE19( for rectification of errors in client200).
Specify the Existing Idoc Number and Executes it .
A Screen is displayed in which you specify the corresponding Function Module as INPUT_IDOC_MATMAS01 and execute it.
10) Execute Tr.code MM03 and give the material as LGMATERIAL
and see that the material is displayed as it was in Client 100.
Now the Material is correctly displayed in Client 200.
11) Monitoring of IDOCS.
Transaction Codes:
IDOC Display of Status: WE 05.
IDOC Date and Time:   WE07.

Frequent Idoc problem

Hi Guru's
We have a major problem on BW and APO. Sometime we have no extraction committed in BW or APO (All extractions of the night).
This is due to Idoc not comitted so to correct the problem we go In SAP R/3 source system transaction SM58 and "Execute in LUW". or after a few hours it commit all extractions itself.
But my problem is that this kind of problem appears once a week and i don't know why. SAP support can't help me because each time they connect, we committed manually or it was done automatically and they answer that they can't investigate.
Thanks for any idea.
Cyril

hi mate, have u checked that you are up to date with the latest firmware along with the latest Nokia system app updates from the Store? also try performing a soft reset, and check that your microSIM card is cut correctly etc.

SAPMEINT - IDOC problem

Hi
I have a weird problem here (I tried only MATMAS). MII gets the IDoc only after 2 sending. Each time I trigger IDoc in ERP, MII does not get it. MII get it only second time. No error in Log.
I deleted the Idoc in MII (Message Monitor ) and SAPMEINT (Queue Monitor - High Perfomance Integration) and tried it again. And it is always the same problem.....first MATMAS no entry , MII get the MATMAS only after 2nd trigger.
any idea?
I am using SAPMEINT High Perfomance.
p/s: I have another machine with SAPMEINT Standard Integration and using other logical system in ERP. MII in this machine receive all the IDOCs.
Any clue
thanks

I found the issue. Another MII server having the same IDOC connection (XMIIIDOC01)
thanks

IDoc to File, SM58 shows error, ST22 short dump - Runtime error

Hi friends,
I am doing a simple IDoc to file scenario using the EVMSTA01 IDoc. My XI is running on client 100 and I am trying to send the IDoc from the client 200 on the same machine. I have completed the design and configuration steps required and also performed the required steps in Sender client (Sm59, we21 and BD54) and receiver client (Sm59, IDX1 and IDX2).
When I tried sending the IDoc from WE19, status meesage says that, the IDoc has been successfully sent to the receiver but SM58 shows error "IDOC_ERROR_WORKFLOW_START_R". When I looked in to ST22, there was a short dump with the below message -
Runtime Errors         MESSAGE_TYPE_X
Date and Time          18.10.2008 23:24:29
ShrtText
     The current application triggered a termination with a short dump.
What happened?
     The current application program detected a situation which really
     should not occur. Therefore, a termination with a short dump was
     triggered on purpose by the key word MESSAGE (type X).
Error analysis
     Short text of error message:
     Unable to read RFC destination WORKFLOW_LOCAL_200
     Technical information about the message:
     Message classe...... "SWF_RUN"
     Number.............. 617
     Variable 1.......... "WORKFLOW_LOCAL_200"
     Variable 2.......... "RFC_READ_DESTINATION_TYPE"
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
     Variable 3.......... "DESTINATION_NOT_EXIST"
     Variable 4.......... " "
Trigger Location of Runtime Error
     Program                                 CL_SWF_RUN_WIM_LOCAL==========CP
     Include                                 CL_SWF_RUN_WIM_LOCAL==========CM07Z
     Row                                     10
Module type                             (METHOD)
Module Name                             IF_SWF_RUN_WIM_UTL_INTERNAL~GET_SYSTEM_USER
rce Code Extract
e SourceCde
1 METHOD if_swf_run_wim_utl_internal~get_system_user .
2   DATA: l_excp TYPE REF TO cx_swf_run_wim.
3
4   TRY.
5       IF me->m_int_state-system_user IS INITIAL.
6         me->m_int_state-system_user = cl_swf_run_workflow_properties=>get_rfc_destination_us
7       ENDIF.
8       re_user = me->m_int_state-system_user.
9     CATCH cx_swf_run_wim INTO l_excp.
>>       MESSAGE ID     l_excp->t100_msg-msgid
11               TYPE   'X'
12               NUMBER l_excp->t100_msg-msgno
13               WITH   l_excp->t100_msg-msgv1 l_excp->t100_msg-msgv2
14                      l_excp->t100_msg-msgv3 l_excp->t100_msg-msgv4.
15   ENDTRY.
16
17 ENDMETHOD.                    "
Any help would be appreciated..!!
PS: Points would be assigned to all the helpful replys without fail

Hi,
See check for RFC destination and it is working as per your configuration or not , i mean , it is trying to locate remote server.. , so try to check in sm59, remote login and the respective result is going to your required client or not ??
Also see the further errors while doing Idoc related scenarios..
IDOc testing - /people/suraj.sr/blog/2005/12/29/generate-test-case-for-an-idoc-scenario
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133 - Idocs not reaching XI. Not posted in the receiver SAP
idoc settings /people/ravikumar.allampallam/blog/2005/02/23/configuration-steps-required-for-posting-idocsxi
idoc erros - http://help.sap.com/saphelp_nw04s/helpdata/en/6a/e6194119d8f323e10000000a155106/content.htm
idoc mapping - /people/james.guanzon/blog/2006/03/23/how-to-support-industry-standards-in-xi-part-ii-of-iii--mapping
IDoc erros troubleshooting - /people/raja.thangamani/blog/2007/07/19/troubleshooting-of-ale-process
Regards
Chilla

Sender RFC-Problem in SM58

Hi all,
Currently I am working on RFC synchronous call with out using BMP.
Here we have developed two asynchronous RFC call to achieve the above requirement.
Here are the details,
1. A call from FILE-XI-RFC (Receiver), for sending the selection criteria
2. Another call from (Sender) RFC-XI-FILE for sending the response back.
Here I am going to call 2 RFCs to get the response back. Here when I am working with the scenario (2) i.e., sender RFC, I have done all the design and configuration part of it.
And when am trying to test this sender rfc from a sample ABAP report (with COMMIT WORK) the RFC gets executed without any error but when I check in SM58 all the back ground tasks gets queued and are not getting processed further.
Can anyone please help me out? Is it a configuration problem in XI or in ABAP.
Please help me. Its very urgent for me.
Thanks in advance,
-kanth.

Hi,
did you try to push the entries in SM58 -> F6 ?
do you see any error ?
also check out my blog:
/people/michal.krawczyk2/blog/2005/03/29/configuring-the-sender-rfc-adapter--step-by-step
to see if your RFC to XI is correct - you can test it from sm59
Regards,
michal
<a href="/people/michal.krawczyk2/blog/2005/06/28/xipi-faq-frequently-asked-questions">XI / PI FAQ - Frequently Asked Questions</a>

Mapping with IDoc problem

Hi All
I am having a problem where if I get over about 30 records from my 3rd Party in a file. This data is mapped to the Materials Master IDoc(MATMAS05) and it gets a mapping error when trying to run thru the mapping.
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_MATCAT_MATMAS_</SAP:P1>
<SAP:P2>com.sap.aii.utilxi.misc.api.BaseRuntimeException</SAP:P2>
<SAP:P3>RuntimeException in Message-Mapping transformatio~</SAP:P3>
If I take this data from the Payload in SXMB_MONI and test in the Graphical Mapping tool in Integration Design it crashes with the above error. If I take this file and break into 2 parts and then send thru the mapping tool both files has no error. Does anyopne have any idea why this error occurs(could this be a memroy error - but for like 30 records) and how I can fix this as we would like to do a mass upload - about 9000 records(materials).
Your help will be appreciated.
Thanks
Clinton

Hi
This is such a weird error.
I have now started taking this file that I receive from the 3rd party with 200 records and tested it with the mapping tool. The results are as follow: From record 1-31 goes successful, 32-147 goes successfully and 148-200 goes successfully. So if I take the file as one file it crash, but if I break the file into the above 3 files it goes thru fine. for the first part it can only take 31 records, the 115, and then the rest. This does not make any sense, can someone please give me some advise.
Thanks
Clinton

G/L Idoc problem

Hi All,
I am posting an invoice from a flat file. First of all i will execute the program RSEINB00 and input the file name. This program will create an idoc from the flat file.
Next, I will execute the program RBDAPP01 to process the idoc and post an invoice.
The problem i am facing is, When there are more no of lines (G/L accounts) in the file ( Say 5948 lines ) the created IDoc data records are as follows.
it has total 47872 segments. And it splits the idoc and each segment block is having 993 lines (G/L accounts).
Segments 000001 007951 - 993 lines
Segments 007952 015951 - 993 Lines
Segments 015952 023951 - 993 Lines
Segments 023952 031951 - 993 Lines
Segments 031952 039951 - 993 Lines
Segments 039952 047872 - 983 Lines.
It will create a BDC session and whn i process the session error comes "No batch input data for screen SAPMF05A 0700" after 949th line. When i see th OSS note it says "Invoices with more than 949 G/L account line items must be split".
My Question is Where can i do this setting inorder to restrict the G/L account lines to <949 in each segment block??
Any insights will be appreciated.

Hi Tushar,
You can add your own codes in user exit to restrict the G/L account lines to < 949 during creation each segment block.
Please search any user exits available in the function module which is used for inbound IDoc creation.
In this case, your BDC will not give an error message because you already handled the max lines for G/L account during creation an IDoc for batch input process.
Hope this will help.
Regards,
Ferry Lianto
Please reward points if helpful.

Inbound INVOIC01 IDOC problem

Hi,
I am working on inboind INVOIC01 idoc and i am facing some problem in that.
When IDOC comes in it is creating application document ( Status 53 ). When i go and check in transaction MIR4 the application document (Invoice) is created. But the problem is, the Invoice is not being posted.
When i see the invoice document, there is not tax code and so the invoice does not show any amount. I do not know why it is happening.
Can anyone let me know what are the all required segments / fields for inbound invoice interface. What are the all configuration options required for it.
Thanks,

Hi Srinivas,
Thanks for your reply.
I have already configured the tax code config and now invoices are created correctly.
But now i have one scenario which i am tying to figure out how to get it right.
Let say for example
Example - 1
- i have PO with 1 line iteam with Quantity = 1 and amount $100. ( we mostly have PO with quantity =1 and only thing matter is $ value )
- If the incoming invoice also have quantity = 1 and amount $100, it works fine.
- But the problem is, sometime vendor sends the partial invoice. that is, quantity = 1 but amount $ 50. There can be multiple invoice with same quantity as PO line item different amount at different time. In this case i am gettng "Account Determination" error ( message M8 147 ). Is there any way i can make this scenarion work. 80% of invoices comes like this. Please let me know
Example - 2
- i have PO with 1 line iteam with Quantity = 2 and amount $200.
- If the incoming invoice also have quantity = 1 and amount $100, it works fine. Also, if it has quant = 2 and amount $ 200 it works fine. In other workds the quantity / amount ratio in invoice matches that of PO, it works fine.
- But in few case we will get invoice with quantity = 1 ( PO as quant = 2) with amount 80 ( infact, any value other than 100. PO has $200, $100 / 1 each ) and in this case invoice is failing too.
Can you please let me know, is there any setting in Logistic Invoice Verification, to support these scenarios.
Thanks
Pratik

Add segment to inbound idoc problem

Hi ,
I want to insert a segment in the middle of the segements inside a inbound idoc processing module.The problem is
i am able to pass the segmnet name and data but i don't now what should be populated to the segment number (SEGNUM). Its value is coming as the same value of the previous segment when i checked in debugging mode.Can any body tell me how to populate the segnum field.
Regards,
Soumya.

Have you tried by just keeping it blank.I will work fine if the hierarchy is kept correctly.

IDOC Error in SM58 and Management Console

Hi Guys,
Good day!
I am currently having issues on sending IDOCs to BODS.
There are instances that an IDOC gets stuck or ends up with an error in transaction code SM58. In transaction WE02, the IDOC is
successfully processed with status 03. In a set of IDOCs (10 or more), one IDOC is in error in SM58, usually the first IDOC gets the error and the next IDOCs are successfully processed. The error received in SM58 displays the following:
Error 1: R3RfcClient(DI_CLIENT)ActaIDocFunc::Process()...
Error 2: CPIC-CALL ThSAPCMRCV no data received
However, the client interface is active/running.
In the management console, the error Logs-History displays the following:
(14.0) 04-08-14 23:32:51 (E) (8060:3868) Unknown: SP(INVOICE_001, ABC:1234)::flowThread() Flow became
invalid during waiting for request (BODI-300137)
(14.0) 04-08-14 23:32:51 (E) (8060:9356) Unknown: R3RfcClient(RFC_CLIENT_INTERFACE) ActaIDocFunc::Process()
encountered processing error for Requeste(15149) (Communication Error. See real time job log for details.) (IDOC 0000001234567890/ABCDE). (BODI-300129)
For the Real-Time Services log, the following is displayed:
(14.0) 04-08-14 23:32:39 (E) (70684:47620) RUN-051005: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS Execution of <Regular Load Operations> for target <IDOC_DETAILS> failed. Possible causes: (1) Error in the SQL syntax; (2) Database connection is broken; (3) Database related errors such as transaction log is full, etc.; (4) The user defined in the datastore has insufficient privileges to execute the SQL. If the error is for preload or postload operation, or if it is for regular load operation and load triggers are defined, check the SQL. Otherwise, for (3) and (4), contact your local DBA.
(14.0) 04-08-14 23:32:50 (E) (70684:68856) DBS-070401: |Session REALTIME_INVOICE|Data flow DATAFLOW_INVOICE|Loader query_IDOC_DETAILS ODBC data source <ABC\ABC,12345> error message for operation <SQLExecute>: <[Microsoft][SQL Server Native Client 10.0]TCP Provider: An existing connection was forcibly closed by the remote host. >.|<Regular Load Operations>|<IDOC_DETAILS>
Given this, I would like to ask on how to eliminate this issue.
Thanks,

Idoc Error in sm58

Hello All,
My Idoc for any Data load is failing in sm58 with "No authorization to send IDocs with message type R SRQST (Message no. SR053)". I have Sap_ALL and All New in both ECC and BID.
Thank you,
Rakesh.

Hi
Please check the SAP Note 150315.
Check whether SAP_ALL is provided for user ALEREMOTE and also cross check whether these two S_BI-WX_RFC and S_BI-WHM_RFC authorizations. are provided.
Thanks

Strange IDoc problem in new System

I am trying to post IDocs through a new production system that has just been set up. We have been running the scenario in the Test environment successfully for a few weeks.
I send a batch of IDocs to the system, for example a bunch of four IDocs. Sometimes all four will process fine, other times one or more of the IDocs gop into error with the message
There is no connection registered at the Messaging System for adapter type: File_http://sap.com/xi/XI/System
If I select the messages in the monitor, I can sometimes get the message through, and sometimes it reverts back to this error, perhaps requiring a few attempts to process successfully. Sometimes the message just will not process.
I am always resenfing four IDocs with the same data, so I really do not know what the problem could be.
Any answers appreciated!
BR,
Tony.

Hi,
NEVER delete the files manually. As a admins we have to follow proper Uninstall and reinstall procedures as above one gentle man said.
Here we will definately have some extra files also, like sapreorg, and backup file manually created if . Those also should be uninstalled properly.
Also, we should maintain one back up copy of our file systems in each servers.
just refer my system file structure, and proceed further.
http://img158.imageshack.us/img158/591/bdfll0.jpg
bye...

IDOC: Problem with data filter for IDOC extension field

Hallo!
I've created an idoc extension for the basic type DEBMAS06 that works fine. Now I want to use a data filter for one field ( company code ) of my segment. Every segment with a company code different from 100 should be filtered and not send to the other client. But what happend is that for all customers that have at least one company code different from 100, all segments including the one with cc 100 were deleted and a error "Segment ... does not exist for message type DEBMAS" appeared on the screen.
Does anyone have any ideas about this problem?

Not sure about changes to be made at the filtering options.
An alternative would be sending the data to XI as it is and perform the mapping to remove the unnecessary segments.
Disadvantage: Unnecessary processing of segment would be done at XI.
Advantage: The integration logic would be completely handled by XI.
Regards,
Prateek

MATMAS outboud Idoc: problem in SM58

Similar Messages

Maybe you are looking for