IDOC FM IDOC_INPUT_ORDRSP

Hi,
I'm creating idocs through FM IDOC_INPUT_ORDRSP.
For some reason the FM is dumping. I'm on SAP 4.7. If I run the FM normally also it is dumping the same way. Could anyone tell me the reason, if they have encountered the same thing.
The dump screen says
SQL error 1105 occurred when accessing program "SAPLEINM " part "LOAD".
Trigger Location of Runtime Error
Program SAPLEINM
Include ????????????????????????????????????????
Is there any note to be installed to avoid this problem?
Message was edited by: vijay srikanth

Check a couple of things. This error is an SQL error related to very complex select statements. But your dump says that is happened when tyring to LOAD. So there is something corrupted.
Go to SE38, enter the program name SAPLEINM and generate. Did you recently upgrade? Did you write any user exits in there?
I didn't find any notes with this error.

Similar Messages

Enhancement for inbound idoc posting(idoc_input_ordrsp)

hi,
please find solution for the below.
business senario: when the vendor send purchase order confirmation through idoc a automated acknowledgement has to be send.
technical: when vendor send idoc (orders05) it updates with FM (idoc_input_ordrsp) our system.
but in the idoc a segment E1EDP19 will have the field IDNLF which has to be filled to send a acknowledgement .
in my case:
the user some times will fill the segment so to get automated acknowledgement we have to write an enhacement to populate the segment in inbound FM.
i have written code in EXIT_SAPLEINM_007. and populated the data in internal table. but the changed data in internal table is not reflecting in processed idoc(in we02 direction 2).

idoc_data is the intenal table which hold all the segment data in run time.
now i fetched matnr from ekpo table populated E1EDP19
and modified the internal table by adding idoc_data-sdata when idoc_data-segnam is E1EDP19 .
ultimately the sdata is reflecting in the idoc_data-sdata for the segment.
but when we check in we02 for the processed idoc the changes are reflecting.
give me a solution for the data to reflect in processed idoc.

Need help in populating Text ID using IDOC ORDERS05

I have following scenario.
PO is being send from ECC to EDI partner.
and we received the PO feedback from the EDI partner
For PO feed back, we are using ORDERS05 idoc type and ORDRSP message type.
Custom Text Id(F01) has been added to the Text tab of the header section of the Purchase order screen (ME23N).
Custom Text id (F02) has been added to the Text tab of the Item section of the purchase order screen.
(Text ID F01 and F02 are in object EKKO - checked in transaction se75)
Now, I m posting idoc with the following value but Text field (in header and item level) is not updating while displaying PO.
Header - E1EDKT1
     TDID -   F01
     TSSPRAS- E
                     TDOBJECT - EKKO
              E1EDKT2
     TDLINE   - "My Header Text"
Item Level - E1EDKT1
     TDID -   F02
     TSSPRAS- E
                     TDOBJECT - EKKO
              E1EDKT2
     TDLINE   - "My Item level Text"
Can we update the Text Id in PO using IDOC ORDRSP.ORDERS05? I have tried but it is not updating
Any suggestion.
Edited by: Chetankumar Patel on Mar 14, 2011 10:17 PM

Have you tried with updating other Long texts ? While going through the code of inbound function module IDOC_INPUT_ORDRSP, it is mentioned that only limited fields are available for updation. See remarks in line no : 88 of include LEINMF2O.
read document and prepare for update P.O. Item fields
* possible Update fields of EKPO: LABNR, IDNLF, NETPR

Creating a Purchase Order using ORDERS05 Idoc

Hi Experts,
I need to create a purchase order using ORDERS05 Idoc, with the data I am using a sales order is gettig created but I need to create a PO insted of SO.
Please let me know what is difference between a PO and SO while using ORDERS05. Also please let me know what are all the fields that needs to chaged in the Idoc.
Thanks,
Suma

Hi,
   I'm looking at a similar problem, can we use ORDERS05 IDOC basic type to create a Purchase Order?
   What is the inbound processing FM? I tried IDOC_INPUT_ORDRSP, but it seem to only allow changes to a PO, and not creation of a PO.
   For IDOC_INPUT_ORDERS FM this one seem to only create Sales Orders?
   Which inbound FM should i be using?
Regards.

Inbound idoc values when updated from user exit not saved

I'm trying to process some user exits of an inbound idoc from WE19.
The values get correctly populated to IDOC_DATA internal tables of IDOC_INPUT_ORDRSP function module in debug kode
but when the new idoc is generated from WE19 , those segment values (populated by exit) are not shown/saved.
The user exit is EXIT_SAPLEINM_007.
Is it not possible to populate segment values of inbound idocs from using user exits. If yes , then during testing using WE19 , every time a new idoc is created it should display those values into the concerned segments. Please help.

Hello,
yes is possible it ...
I think the problem is:
or
you have something wrong when to append the new line on internal table
or
the exit used is not correct: read the documentation on EXIT_SAPLEINM_0**

ORDRSP idoc user exit exit_sapleinm_007

i have problem with inbound EDI for po acknowledgment(855) ,message type used ordrsp process code ORDR and basic type is orders05 and function idoc_input_ordrsp
Vendor is sending only vendor material number (IDTNR) and qualifier 002 is used. During IDOC processing I am using user exit exit_sapleinm_007 to get the SAP material number based on Purchase order number.
In user exit I am trying to collect the SAP number based on vendor number (IDTNR)and purchase order from EKPO table
When processing the segment E1EDP19 using the exit_sapleinm_007, I am unable to pass the PO number (EBELN) and therefore I am unable to extract the corresponding SAP number (Customer Number), which resulted in failure of IDOC.
IDOC error message : Material number differs from the ordered material number.
Purchase order (EBELN) is present in segment E1EDP02 and this segment is processed before E1EDP19.
I am not sure how this can be resolved? Is their any other user exit that can be used for ORDRSP idoc in extracting SAP number (customer material number) from vendor material number (IDTNR)

Hi Ashutosh,
All the exits for listed are too early in the flow for you to know if the DN was created successfully or not, like Christian has suggested you will have to use the customer exits/BAIDs available within "GN_DELIVERY_CREATE" to achieve your requirement. There seem to be a couple of customer function exits available, and a BADI - SHP_BADI_GN_DELIVERY_CREATE try them.
Also calling an FM in update task wouldn't help you, unless you have some key information with which you can check if the DN was successfully created.
Regards,
Chen

Error monitoring through workflow for idoc with message type ORDRSP

Hi All,
Through WE19 I am trying to post a failed idoc ie idoc in 51 status for message type ORDRSP to check whether the event IDOCORDRSP-INPUTERROROCCURED event is triggering or not. Though the idoc is going into 51 status and partner profile is maintained I cannot find this event in SWEL. I checked in fm IDOC_INPUT_ORDRSP fm and found that workflow_result is 99999.
Can anybody tell me why the event is not getting triggered for the message type ORDRSP or where do I debug to find out what is going wrong. IDOC_INPUT_ORDRSP fm is getting called from BUS2012 'S method confirmfromORDRSP which is very strange.So I am not getting where do I debug.
Regards
Suchandra

Hi All,
Solved it by my self.. To trigger the event we need to populate the EDIDC control record in WE19 and press standard inbound button 'not test by inbound fm) and then the inputerroroccured event will trigger...
Regards
Suchandra

Provide ALE and IDOC Faqs and all Transactions

Dear Experts,
I am new to ALE & IDOC.
Please provide ALE & IDOCs FAQs and all Transactions?
Thanks in advance.

<b>FAQS</b>
A L E
Q: Our IDOC remains in status 51 ( not posted) while testing ALE setup by passing DEBMAS02 Idocs. The message 'Field KNA1-BRSCH is not an input field'. This is the Industry key. What are we missing?
A: Go to IMG - menu path IMG->LogisticsGeneral-> Logistics Basic Data: Business partners->Customers-> Control->Define Account groups and field selection for customer.
Select sold-to or ship-to. Select General Data. Select control and double click. Industry key is found here. Change the option to 'Optional Entry'.
Check OSS 5599. You may have to update view V_T078D also.
E D I / IDOC
Q:1 We created an EDI Vendor and created all required output conditions. However no IDOC is generated when PO is printed. Why?
A: Go to Header->output for the PO. The output type shall be '6'. The status shall be '1'. If the status is '0' check the timing. If the status is '2' , go to 'GOTO->Processing Log' and the explanation for non-generation of IDOC can be seen.
Q: How can we create / upload IDOC's from legacy system to SAP?
A: Third party tool Mercator may be used to convert Legacy files to Idoc format. Mercator provides an IDOC tree import facility, SAP provides the export facility. You can transfer the Idoc layouts from SAP to Mercator automatically and then map.
Q: We want to receive an outbound EDI 855 IDOC only if E2EDP20 -scheduling confirmation segment is present. Else get an "error" status preventing triggering the EDI subsystem.
A: User exit logic has to be added in function IDOC_INPUT_ORDRSP.
Set up a test flag and set it off when the IDOC header is read.
Turn the flag ON when the EDP20 segment is read.
Interrogate this flag when the next segment after EDP20 in the same IDOC comes in. If it is on ,you have an EDP20 coming in.
Issue an error status 51 with suitable message for whichever condition you don't want the IDOC to be processed, This will stop the IDOC from posting.
Q: Where ever PO is sent to the vendor via EDI, we want an acknowledgement of the PO by vendor. Which fields are updated and what should be my procedure?
A: Execute Program: IDOC_INPUT_ORDRSP
Process code: ORDR
Message type: ORDRSP
IDOC: ORDERS01
The confirmation process allows the supplier to return an acknowledgment. Only Dates and quantities can be changed The information is stored in the PO and can be viewed via Item->Confirmation->Overview. The PO can be flagged as 'confirmation required' so that Pos without acknowledgement receipt can be monitored. Control keys and tolerances (days and quantities) have to be customized.
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
Just follow the procedure
Sending System(Outbound ALE Process)
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Create Model View
Tcode BD82 ? Generate partner Profiles & Create Ports
Tcode BD64 ? Distribute the Model view
Message Type MATMAS
Tcode BD10 ? Send Material Data
Tcode WE05 ? Idoc List for watching any Errors
Receiving System(Inbound ALE )
Tcode SALE ? for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 ? Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 ? Idoc List for inbound status codes
ALE IDOC Steps
Sending System(Outbound ALE Process)
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Create Model View
Tcode BD82 !V Generate partner Profiles & Create Ports
Tcode BD64 !V Distribute the Model view
This is Receiving system Settings
Receiving System(Inbound ALE )
Tcode SALE ?3 for
a) Define Logical System
b) Assign Client to Logical System
Tcode SM59-RFC Destination
Tcode BD64 !V Check for Model view whether it has distributed or not
Tcode BD82 -- Generate partner Profiles & Create Ports
Tcode BD11 Getting Material Data
Tcode WE05 !V Idoc List for inbound status codes
Message Type MATMAS
Tcode BD10 !V Send Material Data
Tcode WE05 !V Idoc List for watching any Errors
STEP 1)a Goto Tcode SALE
Click on Sending & Receiving Systems-->Select Logical Systems
Here Define Logical Systems---> Click on Execute Button
go for new entries
-System Name : ERP000
-Description : Sending System
-System Name : ERP800
-Description : Receiving System
press Enter & Save
it will ask Request
if you want new request create new Request orpress continue for transfering the objects
B) goto Tcode SALE
Select Assign Client to Logical Systems-->Execute
000--> Double click on this
Give the following Information
-Client : ERP 000
-City :
-Logical System
-Currency
-Client role
Save this Data
Step 2) For RFC Creation
Goto Tcode SM59-->Select R/3 Connects
Click on Create Button
RFC Destination Name should be same as partner's logical system name and case sensitive
to create the ports automatically while generating the partner profiles
give the information for required fields
RFC Destination : ERP800
Connection type: 3
Description
Target Host : ERP000
System No:000
lan : EN
Client : 800
User : Login User Name
Password:
save this & Test it & RemortLogin
STEP 3) Goto Tcode BD64 -- click on Change mode button
click on create moduleview
short text : xxxxxxxxxxxxxx
Technical Neme : MODEL_ALV
save this & Press ok
select your just created modelview Name :'MODEL_ALV'.
goto add message type
Model Name : MODEL_ALV
sender : ERP000
Receiver : ERP800
Message type :MATMAS
save & Press Enter
STEP 4) Goto Tcode BD82
Give Model View : MODEL_ALV
Partner system : ERP800
execute this by press F8 Button
it will gives you sending system port No :A000000015(Like)
STEP 5) Goto Tcode BD64
select the modelview
goto >edit>modelview-->distribute
press ok & Press enter
STEP 6) goto Tcode : BD10 for Material sending
Material : mat_001
Message Type : MATMAS
Logical System : ERP800
and Execute
STEP 7)goto Tcode : BD11 for Material Receiving
Material : 100-300
Message Type : MATMAS
and Execute --> 1 request idoc created for message type Matmas
press enter
Here Master Idoc set for Messge type MATMAS-->press Enter
1 Communication Idoc generated for Message Type
this is your IDOC
Change Pointers
how to change the description of a material using ALE Change Pointers.
I will give the following few steps
1) Tcode BD61---> check the change pointers activated check box
save and goback.
2) Tcode BD50---> check the MATMAS check box save and comeback.
3) Tcode BD51---> goto IDOC_INPUT_MATMAS01 select the checkbox save and comeback.
4) Tcode BD52---> give message type : matmas press ok button.
select all what ever you want and delete remaining fields.
save & come back.
5) 5) go to Tcode MM02 select one material and try to change the description and save it
it will effects the target systems material desciption will also changes
6) goto Tcode SE38 give program Name is : RBDMIDOC and Execute
give Message type : MATMAS and Executte
ALE/IDOC Status Codes/Messages
01 Error --> Idoc Added
30 Error --> Idoc ready for dispatch(ALE Service)
then goto SE38 --> Execute the Program RBDMIDOC
29 Error --> ALE Service Layer
then goto SE38 --> Execute the Program RSEOUT00
03 Error --> Data Passed to Port ok
then goto SE38 --> Execute the Program RBDMOIND
12 Error --> Dispatch ok
Inbound Status Codes
50 Error --> It will go for ALE Service Layer
56 Error --> Idoc with Errors added
51 Error --> Application Document not posted
65 Error --> Error in ALE Service Layer
for 51 or 56 Errors do the following steps
goto WE19 > give the IDOC Number and Execute>
Press on Inbound function Module
for 65 Error --> goto SE38 --> Execute the Program RBDAPP01 then your getting 51 Error
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
<b>Reward Points if it helps,</b>
Satish

'Purchasing document does not exist' error while testing Inbound PO Idoc

Hi experts,
i am working on Inbound PO Idoc scenario. I am testing Idoc in WE19 with ORDRSP mesage type.
Idoc type:ORDERS05
Process code:ORDR
FM:IDOC_INPUT_ORDRSP
while trying to create PO it is giving an error 'Purchasing document does not exist' in we05.
please suggest me how to resolve this???
Regards,
Bhuvan.

Hi,
first time i am testing this IDoc and i don't find any field in Idoc structure to provide purchase order value.
any more inputs plz??
regards,
bhuvan.

Process of inbound idoc

Hi,
can any one pls let me know the steps we should fallow in an inbound idoc processing.
I have the messagte type , basic type, process code and i have to create partner profile , pls let me know what are the steps to be fallowed
thanks,
Deepak

Hi,
U need to update the Purchase Order based on the idoc.
The Process Code for this development is: ORDR,
Basic IDOC Type: ORDERS05
Function Module: IDOC_INPUT_ORDRSP,
Message type: ORDRSP.
Enhancement: MM06E001
Customer Enhancement: EXIT_SAPLEINM_008
The logic should be written in the Include ZXM06U20.
LOOP AT idoc_data.
CASE idoc_data-segnam.
WHEN 'E1EDP01'.
Move Structure ACKNOW_PO info to Confirmations.
ENDCASE.
ENDLOOP.
Regards
Kannaiah

IDOC_INPUT_ORDRSP LOEKZ = 'L'

Hi all,
anybody know how can I delete a PO item using function IDOC_INPUT_ORDRSP (idoc type ORDERS05).
I set E1EDP01-ACTION = '003' AND E1EDP20-ACTION = '003',
I have implemented note no 66192 and 890812.
The result is that in the PO item confirmation when I set action = '003' I see that LABNR (Order Acknowledgement) i see the string "reject". But no LOEKZ status and MRP changes.
Please help.
Marianna
PS: SAP _APPL 500

Check a couple of things. This error is an SQL error related to very complex select statements. But your dump says that is happened when tyring to LOAD. So there is something corrupted.
Go to SE38, enter the program name SAPLEINM and generate. Did you recently upgrade? Did you write any user exits in there?
I didn't find any notes with this error.

Allow dialogue processing for IDOC_INPUT_ORDRSP

We want to allow dialogue processing for the IDOC_INPUT_ORDRSP FM. When an idoc is recieved and has errors we want to be able to process it using the dialogue screens to correct errors. We do this now with IDOC_INPUT_ORDERS. We have changed the entry in TBD51 that is supposed to denote dialogue processing. It still does not allow the dialogue screens to come up when we process the idoc for the ORDRSP. Does anyone know if there is another place we have to make a setting change to allow this or is there a problem with allowing dialogue processing for certain FMs?

After looking into this further I have found that the TBD51 table should not have been changed. There is actually no way using the standard inbound FM to allow dialogue processing for this particular one. The logic does not exist in the program. We are going to look into workflow to see if there are some business objects that will allow us to perform what we need to do.

PORDCR - Inbound IDOC via User-Exit

Hi All,
I would like to create a Purchase Order via an inbound Idoc with a message type PORDCR.
I would like to make use of the enhancement MM06E001 and the function module EXIT_SAPLEINM_002 to populate data segments.
Please advise if this is the correct user-exit to process an inbound idoc.
Any input appreciated.
Meghna

Hi Meghanarrao,
IDOC_INPUT_ORDRSP-->PERFORM fill_data_ordrsp-->and find the below user exits for each segment...
List of user exits available for --
EXIT_SAPLEINM_001
EXIT_SAPLEINM_002
EXIT_SAPLEINM_003
EXIT_SAPLEINM_004
EXIT_SAPLEINM_005
EXIT_SAPLEINM_006
EXIT_SAPLEINM_007
EXIT_SAPLEINM_008
EXIT_SAPLEINM_009
EXIT_SAPLEINM_011
EXIT_SAPLEINM_012
EXIT_SAPLEINM_013
EXIT_SAPLEINM_014
EXIT_SAPLEINM_015
EXIT_SAPLEINM_016
EXIT_SAPLEINM_017
EXIT_SAPLEINM_018
EXIT_SAPLEINM_019
EXIT_SAPLEINM_020
IDOC----- Dir -Enhancemnt --Description
ORDCHG -O -MM06E001   -- Purch. Ord. Change
ORDCHG- I -VEDB0001     --Sales Ord. Change
ORDERS- O -MM06E001   --Purchase Orders
ORDERS -I- VEDA0001     --Sales Orders
ORDRSP -O- SDEDI001    --Order Confirmation
ORDRSP -I- MM06E001    --Order Response for Purchase Order   "This is the Right one for Purchase order create
IDOC           Msg        ANSI EDIFACT I O
ORDERS01 ORDCHG 860 ORDCHG X X
ORDERS01 ORDERS 850 ORDERS X X
ORDERS01 ORDRSP 855 ORDRSP X X
IDOC_INPUT_ORDRSP--Function module-BUS2012-Inbound-Purchase order / order confirmation
regards,
Prabhudas

Inbound ORDRSP idoc

I'm getting error 'Purchasing Document does not exist' when trying to process an inbound ORDRSP (855 EDI document). Has anyone seen this before? Thanks!

Hello Susan
Most likely fm IDOC_INPUT_ORDRSP is responsible for processing this inbound IDoc.
Try to execute your failed IDoc using transaction WE19 and debug this fm. If it creates a batch input then you can execute the recording in mode 'A' (= display screens) which will show you the problem.
Regards
Uwe

Logical System in IDOC-XI scenario

Hi,
I need help to understand few things in IDOC-XI scenario, could any one help me in this regard.
we use Adapter specific identifiers to map services, we have following type of identifiers 1) Sys.ID & Client No. 2) Logical System.
my questions are
a) Are we use Logical System in B to B scenario ?
b) Are we use LS in reference to the SAP system or Non SAP system ? if a non SAP system....how a non SAP system send an IDOC and why a non SAP system receive an IDOC ( conversion is possible in XI ) ?
Thanks and Regards
Mahesh.

Hay Kumar,
Logical systems can also be used for SAp sytems wich are not installed yet as a virtuall placeholder.
a) yes. if on of your business is a non sap system or a propritery system that you developed yuo'll ue LS.
b) non SAP system can send and recieve IDOCs. so it's possiable to get an IDOC from a system and turn it into an RFC for SAP or get an IDOC from an SAP system and then turn it into something else for another system.
Have a Good One,
Uri Lifshitz.

IDOC FM IDOC_INPUT_ORDRSP

Similar Messages

Maybe you are looking for