Debugging EDI output (IDOC creation) for purchase order...

Hi,
We have a EDI output type defined for Purchase order. When I go to Messages tab in ME22N transaction and repeat the EDI output and save it, it creates a IDOC which I can see using transaction WE02.
Now the problem is there is a user exit which I know gets triggered, when the IDOC is created for this PO. When we do some changes in this user exit, I see those changes are reflected when new IDOC is created. But if I put breakpoint, and do repeat output -> save, the debugger does not stop there.
Is there is some technique I can see the breakpoint stoppage in user exit for IDOC creation during EDI output for Purchase order ?
Regards,
Rajesh

Hi
Youc can set the output Peridoically (After Giving the output type, set the furthere data as periodic).
Save.
Set the break point in your user exit.
Go to se 38 -> Run RSNAST00,
Give the object id (Your PO #)
Give the output type and execute, the control will stop at break point.
Regards,
Baburaj

Similar Messages

Output type configuration for Purchase order

Dear Friends,
I want to configure output type for Purchase order in retail system and later want to trigger it in AFS(apparel, footwear solution) system.
There is integration in IS retail and AFS system.
I created a PO in IS retail system.
Let me know the steps how can I get the IDOC triggered when I go and check in PO header. GO to>Messages?
Any pointers.
Regards
Ashu

Answered.

IDOC Types for Purchase Orders, Vendor Master and Goods Receipt

Hello All,
Can any have idea about the IDOC Types that can be used for triggering when the actions creation/change/deletion on Purchase Orders or Vendor Master or Goods Receipt is performed?
Please let me know the names of IDOC Type, Process Codes, message type... and all the other required information...
Thanks in Advance,
Kumar.

Hello Ferry,
Thanks again for the IDOC Types. I have another question. Can we use those IDOC types for creating/changing/deletion of Purchase orders or Vendor Master or Goods Receipt happens? I mean can we configure in such a way that when ever there is a change or deletion of PO or VM or GR happens?
I have got to know about the IDOC PORDCH01 which can be used for Purchase Order. Can u suggest me which can be used for PO's?
Regards,
Phani.
Message was edited by:
Sivapuram Phani Kumar

Inbound Delivery Idoc processing for Purchase Order

We are trying to create a Inbound Delivery for purchase order. We are using idoc basic type DELVRY03.
When we are processing this Idoc we are constantly getting error :
Item 00000 of purchasing document does not exist
Message no. ME706
Diagnosis
Purchase order 00000 with item was not found.
Procedure
Enter a different purchase order.
We have mapped the PO and PO Item fields to Idoc segment fields E1EDL24-VGBEL and VGPOS respectively.
Let me know if anyone came across or know the reason for this message and remdy.
Thanks in advance.

Hi Milind,
Did you get this to work?
Thanks,
Finbarr

Output Message Determination for Purchase Order

Hi all !
Can anybody please explain in brief, the procedure for Ouyput message determination for Purchase order. (including printer settings)
I have tried it throgh the Standard Configuration guide. but i am not able to do.
Please explain step by step including form attachment.
Thanks in Advance !!!!

Hi,
Customization steps for Output of Purchase Order
1. Condition Table
SPRO > Material Management> Purchasing -> Message -> Output Control->Condition Tables->Define Condition Table for Purchase Order
Select:
Purchasing Doc. Type,
Purch. Organization,
Vendor
2. Access Sequences
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Access Sequences->Define Condition Table for Purchase Order
3. Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Types->Define Message Type for Purchase Order
4. Message Determination Schemas
4.1. Message Determination Schemas
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Maintain Message Determination Schema
4.2. Assign Schema to Purchase Order
SPRO -> Material Management-> Purchasing -> Message -> Output Control->Message Schema->Define Message Schema for Purchase Order-> Assign Schema to Purchase Order
5. Partner Roles per Message Type
SPRO -> Material Management-> Purchasing -> Message -> Output Control-> Partner Roles per Message Type ->Define Partner Role for Purchase Order
6. Condition Record
Navigation Path: SAP Menu-> Logistics -> Material Management -> Purchasing-> Master data->Messages-> Purchase Order-> MN04-> Create
Now you create PO (ME21N) and save it. Go to ME22N and print the PO by giving output type.
Note1
Now Check in SPAD (Printer settings) settings & try to check the printer configuration. Check Device attributes, Access methods etc. are maintained in Spool Administration (SPAD) for the selected printer (your local Printer, may be ur using HP01or any but in SAP std is LP01) but consult with your basis consultant regarding above.
Check the following also:
Spool generated using SP01 or SP02.
Output device.
Local printer settings.
Paper Tray, Print Mode, Printer
Note2:
Check MN04 and NACE t.codes
Regards,
Biju K

User Exit IDOC creation - When purchase order gets created

Hi All,
The requirement is whenever user creates a Purchase Order in the current SAP system an IDOC needs to get created and be sent to another SAP system where a Sales Order will be created.
Can anybody suggest the correct User exit/enhancement at the time of Purchase order creation which could be used ?
Also the function modules for creating the IDOCs within the user-exit.
Thanks for your help.

Hi Meghna,
Your requirement is SAP standard function which means you don't have to use any user exit.
What you need to do is configure output control, then when a PO saved, a idoc will send to vendor automaticly.
Here is a step brief
1. configure output type in NACE
2. Add condition record in NACE
3. Setup partner profile in WE20
if you need detailed doc, give me your email, I can send you.
Regards,
Brown

EDI Output not proposed in purchase order

Hi,
Trying to setup an EDI output to the purchase order and the new output is not appearing in the purchase order automatically. Strange thing is the output analysis shows the condition record is found and says "An output proposal created" ! The output appears in the drop down list, able to select it manually and create an idoc.
Did the following steps, but still missing some thing. Please help.
- Created new EDI condition type and assigned std SAP EDI processing routine.
- Assigned output type to PO output schema with manual only unchecked.
- Maintained condition record in MN05.
- Access sequence and access are fine.
Thanks in advance.
Regards,
Krishna.

Hi
Please create the condition record using MN04, instead of MN05
Thanks & regards
kishore

Outbound Idoc creation after Purchase Order Creation via Trading contract

Hi All,
Below is my requirement-
Purchase Order Will be created automatically through trading contract.
I need to pass some details about the purchase order created to the external system through IDOCS.
ie this idoc should get triggered whenever a Purchase Order is created through Trading contract.
Are there standard function modules which can trigger idoc whenever Purchase Order is created through Trading Contract?
Please suggest how to go about it.
Thanks in advance.

Hi Tejas,
Ask your functional consultant to create a new output type for this Purchase order. Attache RSNASTED program and EDI_PROCESSING routine to that output type.And also maintain partner profile for the partner to whom you want to send PO.There is a standard process code ME10 to send Purchase order data.Assign this process code and your new output type in the message control tab of the outbound partner profile view.Hope this helps.
Thanks & Regards,
Kalyan.

User Specific Output Message Determination for Purchase Orders

Hi Sap Experts,
Is there any functionality in SAP where you can setup specific Output message determination for a user?
For example whenever User A creates a purchase order through ME21N it will always be emailed to vendor, whereas for User B whenever they create purchase orders it will always be printed.
Is this possible?

There is no standard functionality with in SAP.
To achieve this Create 2 output types accordingly and create customized tables with user id fields

Different interfaces for purchase order output from MM system

Dear Guru's,
We are configuring the business scenarios of service procurement classic and Plan driven procurement with supplier enablement in the MM-SUS environment for our SRM7.01/ECC6 ehp 5 combination.
These two scenarios are using different interfaces for purchase order output.
The service procurement classic is using the proxy interface PurchaseOrderERPRequest_
Out_V1 for purchase order output from ERP.
However, the plan driven procurement uses the interface ORDERS.ORDERS02 for idoc message for purchase order output from ERP.
Why are there two different interfaces for the same document output in two different business scenario? How the system will determine which interface needs to be used in the runtime for the purchase order output?
Any thoughts will be highly appreciated.
Thanks and regards,
Ranjan

Hi Ranjan,
Please add the value 'CL' in the table SWF_CATIDS
Then it will work.
With Regards,
Malay

Problem in using output type for purchase order

Hi experts,
I am using output type for first time so may be i have done wrong configuration for po output type.The steps i have done are :-
1) Going to tcode NACE->Selected the row u201CEF Purchase Orderu201D and clicked on u201CProcedures".
2) In procedures there are 2 procedures for the application EF (Purchase Order). To proceed further, we would need to find out the procedure that is currently active.Gone to transaction SPRO. In this, navigate as Materials management -> Purchasing ->Messages -> Output control -> Message Determination Schemas ->Define Message Schema for Purchase Order
3) Clicking on u201CAssign Schema to Purchase Orderu201D. So, the procedure RMBEF1 is active for EF (Purchase Order) .
4) Go back to transaction NACE. Select u2018EFu2019 and click on u201COutput typesu201D.
5) Let us use the output type u201CNEU name purchase orderu201D for this purpose. Double-click on NEU.
6) Ensured that the checkboxes u201CAccess to conditionsu201D and u201Cmultiple issuingu201D are checked and the access sequence is 0001(DocType/PurchOrg/Vendor).Only 0001 and 0002 is available in f4 help for this.
7) Now clicked on u201CProcessing Routinesu201D on the left hand side. Ensured that there is an entry for Medium u2018Au2019 (Distribution ALE).
8) After that going back to the main screen of NACE. Select EF (Purchase Order) and clicked on u201CCondition Recordsu201D.
Select NEU and clicked on u201CCondition recordsu201D. The pop-up box appears that gives three radio button option :-
1) Purchasing output determination :purchasing org / vendor for EDI
2) Purchasing output determination :doc. type / purchasing org /vendor
3) Purchasing output determination :document type
but it is not having option only for purchasing organisation through which we can send idoc for changes or creation of PO in that particular pur.org now if i choose 2) i have to give doc type and purchasing org both bcoz they are mandatory fields and value for vendor.
9) Also i have done the necessary ALE configuration (not covered in this document). In the partner profiles, use the message type u201CORDERSu201D and the IDOC type u201CORDERS05u201D.In the tab u201CMessage Controlu201D, used the process codes u201CME10u201D and u201CME11u201D for u201CPO Createu201D and u201CPO Changeu201D respectively.
but the idoc is not generated many times when po is changed and when once it is generated it is giving error
Please suggest solution.
Thanks in advance
nehavt

In me22n in messages tab after looking into processing log it is giving->No recipient found for message type ORDCHG in the
ALE model ,next time giving error as no idoc items belonging to purchasing document found,when i changed message type to ORDCHG the status is green in messages tab it is giving-> error occured while idoc xyz is sent and in WE02 status is red 02
error passing data to port(could not find code page for receiving system)

Creating an IDOC for purchase order

Hello gurus,
I want to generate an IDOC for purchase order.
The Logical System, RFC connection, ports definition is already defined.
In my system i have 800 client as source/sender and 100 client as target/reciever.
On Outbound side-> In Partner profile
I defined-
1. Partner No.- devclnt100
2.Type- US (User)
3. Agent - SAPUSER
In Outbound parameters-
I created message type as Orders.
One thing to note that my partner system is LS i.e. Logical System
Then in Outbound Options-
I mentioned Reciver Port - 800Port
Output Mode- I selected "Transfer Idocs immediately"
& "Do not start subsystem"
In Idoc type-
I gave following information-
Basic Type - Orders05
In Message Control tab i mentioned-
Application - EF
Message Type - NEU
Process Code - ME10
In NACE Transaction Code-
I selected EF Purchase Order as my condition for output control
In that- In output types-
I selecte NEU and double clicked. I checked whether Access to Conditions check box is checked and multiple issuing is checked.
In Dialog structure-Processing routines I checked that -
For Output type - NEU
Application - EF
Processing routines are defined-
medium-Distribution ALE
Program -RSNASTED
Form Routine - ALE_PROCESSING
I think these are the very basic settings that need to be done for creation of Idoc.
Now when i create a PO and then SAVE it an IDOC must be generated.
But when i go to transaction Code WE02. It shows me message "No Idocs genereated".
What is the problem? Where am i going wrong?

Hi Yayati,
Here are all the settings that you need to do. I am not sure which all settings are present so kindly confirm.
Sending side Client800:
1. WE20 - under LS - Outbound parameters - message type = Orders , basic type = Orders05
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
3. NACE - App = EF - Output Types - Processing Routines - Add medium = A (Distribution (ALE)) , Program = RSNASTED, Routine = ALE_PROCESSING.
4. NACE - App = EF - Output Types - Partner Functions - Add medium = Distribution (ALE), Funct = VN.
5. Name - App = EF - Condition Records - Output type = NEU , Choose ur combination (Mine is DocType/Purc Grp)
Pur.Doc Type = NB (Execute) , Add row Medium = A ,Function = VN and other details u choose.
Receiving side Client100:
1. WE20 - under LS - Inbound parameters - message type : Orders ; Process Code : ORDE
2. BD64 - message type - sender = client800, receiver = client100, message type = Orders
For the PO which you have created, go to the PO in ME23N, click on messages .
There should be a line : Output = NEU, Medium = Distribution (ALE)... etc.
If its present then the configuration was correct.
If it has a yellow triangle means it was not processed.
Regards,
Jovito.
Edited by: dsouzajovito on Dec 30, 2010 10:24 AM

Production Order : OUTPUT Type Configuration for Production Order as EDI

Dear SDN All ,
OUTPUT Type Configuration for Production Order.
Doubt in third Point
We have found the IDoc " LOIPRO01 " for Production Order
(Please confirm that this IDoc can be used for outbound IDoc for Production Order)
And foloowing
1. Defining the Output Type for Particular Application.
 T-Code: NACE
A. Output type have created upder application "ME" description : "Inventory Management"
B. " ZEDI " created for getting output as EDI type
 ZEDI is copied from "WF01" output type. and
 Transmision mediam as "EDI"
 Program : RSNASTED
 Form Routine : EDI_PROCESSING
 (Please confirm is this for IDoc creation)
2. Partner profile creation:
A. Partner profile created under logical system and
B. and In outbound parameter declared as "LOIPRO"(This is for sending the IDoc "LOIPRO01" to XI system).
3. Customization for output type for Proction Order -- (For CO02,CO08) ---
 A. But only one functional customization is remaining to do, for getting the IDoc while saving the Production Order in T-Code "CO02" and "CO08"
 For Example:
 in sales order transaction va02 (in DBI 450 client) and select any Sales order.
 & select following menu path.
 Extras --- > Output -
> Header -
> output
 Here we can set our output type "that U defined in NACE Transaction-Code"
 Like the same way I want to set output type for CO02, CO08 transaction.
But I couldn't find the menu Item in Co02 and Co08 for setting the output.(like VA03)
Please help me out for setting the output type for Production Order Creation.
Thanks in advance,
Dhanabal T
Message was edited by: Dhanabal T

Hello.
I have a similar requirement. Did you guys find the solution?

Error:-document is in transfer for purchase order..creation is not possible

Hello,
While doing confirmation of PO I am getting this error, saying "document is in transfer for purchase order..creation is not possible".
can anyone please suggest me solution on this type of error?

Hi,
Is the PO in ORDERED status? Is there any confirmation posted for this PO which might be stuck (idoc failed to reach back end)?
If it is a case of idoc failure, then reprocess the idoc and then do the next confirmation.
regards,
MRao

Getting errors when iam using BAPI_PO_CREATE1 for Purchase Order creation

Hi sap Gurus,
I am getting Errors when iam using BAPI_PO_CREATE1 for Purchase Order creation that Material (144) does not exist but it is alreardy maintained in MM01.
I dont get how it is coming.and what are the mandatory fields in bapi BAPI_PO_CREATE1 in item level .that is too material only.
pls let me know .
thanks in advance.

Hi,
Check the sample code..
report zpo_test             .
*DATA DECLARATION
constants : c_x value 'X'.
*Structures to hold PO header data
data : header like bapimepoheader ,
headerx like bapimepoheaderx .
*Structures to hold PO account data
data : account like bapimepoaccount occurs 0 with header line ,
accountx like bapimepoaccountx occurs 0 with header line .
*Internal Tables to hold PO ITEM DATA
data : item like bapimepoitem occurs 0 with header line,
itemx like bapimepoitemx occurs 0 with header line,
*Internal table to hold messages from BAPI call
return like bapiret2 occurs 0 with header line,
*Internal table to hold messages from BAPI call
pocontractlimits like bapiesucc occurs 0 with header line.
data : w_header(40) value 'PO Header',
purchaseorder like bapimepoheader-po_number,
delivery_date like bapimeposchedule-delivery_date.
data : ws_langu like sy-langu.
*text-001 = 'PO Header' - define as text element
selection-screen begin of block b1 with frame title text-001.
parameters : company like header-comp_code default '122' ,
doctyp like header-doc_type default 'NB' ,
cdate like header-creat_date default sy-datum ,
vendor like header-vendor default '2000000012' ,
pur_org like header-purch_org default 'PU01' ,
pur_grp like header-pur_group default '005' .
*sociedad like HEADER-COMP_CODE default '122' ,
*vendedor like HEADER-SALES_PERS default 'sale person'.
selection-screen end of block b1.
selection-screen begin of block b2 with frame title text-002.
parameters : item_num like item-po_item default '00010',
material like item-material default '12000000' ,
tipo_imp like item-acctasscat default 'K' ,
*pos_doc like ITEM-ITEM_CAT default 'F' ,
shorttxt like item-short_text default 'PRUEBA BAPI' ,
grup_art like item-matl_group default '817230000' ,
plant like item-plant default '3001' ,
mpe like item-trackingno default '9999' ,
*contrato like ITEM-AGREEMENT default '4904000003' ,
*quantity like ITEM-QUANTITY default 1 .
po_unit like item-po_unit default 'EA'.
selection-screen end of block b2.
Par?mnetros de imputaci?n
selection-screen begin of block b3 with frame title text-004.
parameters : centro like account-costcenter default '1220813150',
cuenta like account-gl_account default '6631400' ,
num_pos like account-po_item default '10' ,
serial like account-serial_no default '01' ,
ind_imp like account-tax_code default 'I2' .
selection-screen end of block b3.
start-of-selection.
*DATA POPULATION
ws_langu = sy-langu. "Language variable
*POPULATE HEADER DATA FOR PO
*HEADER-COMP_CODE = sociedad .
header-doc_type = doctyp .
header-vendor = vendor .
header-creat_date = cdate .
header-created_by = 'TD17191' .
header-purch_org = pur_org .
header-pur_group = pur_grp .
header-comp_code = company .
header-langu = ws_langu .
*HEADER-SALES_PERS = vendedor .
*HEADER-CURRENCY = 'DOP' .
*HEADER-ITEM_INTVL = 10 .
*HEADER-PMNTTRMS = 'N30' .
*HEADER-EXCH_RATE = 1 .
*POPULATE HEADER FLAG.
headerx-comp_code = c_x.
headerx-doc_type = c_x.
headerx-vendor = c_x.
headerx-creat_date = c_x.
headerx-created_by = c_x.
headerx-purch_org = c_x.
headerx-pur_group = c_x.
headerx-langu = c_x.
*HEADERX-sales_pers = c_x.
*HEADERX-CURRENCY = c_x.
*HEADER-ITEM_INTVL = c_x.
*HEADER-PMNTTRMS = c_x.
*HEADER-EXCH_RATE = c_x.
*HEADER-EXCH_RATE = c_x.
*POPULATE ITEM DATA.
item-po_item = item_num.
item-quantity = '1'.
*ITEM-MATERIAL = material .
item-short_text = 'prueba bapi_po_create1'.
*ITEM-TAX_CODE = ''.
item-acctasscat = 'K' .
*ITEM-ITEM_CAT = 'D' .
item-matl_group = '817230000' .
item-plant = '3001' .
item-trackingno = '99999'.
item-preq_name = 'test'.
*ITEM-AGREEMENT = '' .
*ITEM-AGMT_ITEM = ''.
item-quantity = '1' .
item-po_unit = 'EA'.
*ITEM-ORDERPR_UN = 'EA'.
item-conv_num1 = '1'.
item-conv_den1 = '1'.
item-net_price = '1000000' .
item-price_unit = '1'.
item-gr_pr_time = '0'.
item-prnt_price = 'X'.
item-unlimited_dlv = 'X'.
item-gr_ind = 'X' .
item-ir_ind = 'X' .
item-gr_basediv = 'X'.
*ITEM-PCKG_NO = '' .
append item. clear item.
*POPULATE ITEM FLAG TABLE
itemx-po_item = item_num.
itemx-po_itemx = c_x.
*ITEMX-MATERIAL = C_X.
itemx-short_text = c_x.
itemx-quantity = c_x.
*ITEMX-TAX_CODE = C_X.
itemx-acctasscat = c_x.
*ITEMX-ITEM_CAT = c_x.
itemx-matl_group = c_x.
itemx-plant = c_x.
itemx-trackingno = c_x.
itemx-preq_name = c_x.
*ITEMX-AGREEMENT = C_X.
*ITEMX-AGMT_ITEM = c_x.
itemx-stge_loc = c_x.
itemx-quantity = c_x.
itemx-po_unit = c_x.
*ITEMX-ORDERPR_UN = C_X.
itemx-conv_num1 = c_x.
itemx-conv_den1 = c_x.
itemx-net_price = c_x.
itemx-price_unit = c_x.
itemx-gr_pr_time = c_x.
itemx-prnt_price = c_x.
itemx-unlimited_dlv = c_x.
itemx-gr_ind = c_x .
itemx-ir_ind = c_x .
itemx-gr_basediv = c_x .
append itemx. clear itemx.
*POPULATE ACCOUNT DATA.
account-po_item = item_num.
account-serial_no = serial .
account-creat_date = sy-datum .
account-costcenter = centro .
account-gl_account = cuenta .
account-gr_rcpt = 'tester'.
append account. clear account.
*POPULATE ACCOUNT FLAG TABLE.
accountx-po_item = item_num .
accountx-po_itemx = c_x .
accountx-serial_no = serial .
accountx-serial_nox = c_x .
accountx-creat_date = c_x .
accountx-costcenter = c_x .
accountx-gl_account = c_x .
account-gr_rcpt = c_x.
append accountx. clear accountx.
*BAPI CALL
call function 'DIALOG_SET_NO_DIALOG'.
call function 'BAPI_PO_CREATE1'
    exporting
      poheader         = header
      poheaderx        = headerx
    importing
      exppurchaseorder = purchaseorder
    tables
      return           = return
      poitem           = item
      poitemx          = itemx
      poaccount        = account
      poaccountx       = accountx.
*Confirm the document creation by calling database COMMIT
call function 'BAPI_TRANSACTION_COMMIT'
exporting
wait = 'X'
IMPORTING
RETURN =
end-of-selection.
*Output the messages returned from BAPI call
loop at return.
    write / return-message.
endloop.
Regards
Sudheer

Debugging EDI output (IDOC creation) for purchase order...

Similar Messages

Maybe you are looking for