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

Similar Messages

IDOC/BAPI for Production order creation from Legacy system

Hi all
We are using an interface to create Production orders from legacy to SAP. Would you recommend an IDOC or a BAPI to create Production orders. If IDOC or BAPI then could you please mention which one?
thanks a bunch

Hi John,
For your purposes, please use BAPI for production order creation from legacy system. There is no standard inbound IDoc available to use. SAP has an IDoc for outbound interface only (message type LOIPRO).
If there is an inbound IDoc available, I would recommend to use an IDoc.
IDoc technology has excellent error handling and will allow you to reprocess an error (if any).
BAPI is also good approach to use and fast in term of processing.
For BAPI approach, you can use BAPI BAPI_PRODORD_CREATE.
Hope this will help.
Regards,
Ferry Lianto

Number of messages for Purchase Order output

Hi All!
I have to set the number of messages for the Purchase Order output at 2 (NAST-ANZAL). For a certain output type, in the Communication method the default value for Number of messages (original + copies) has to be 2. There is a transaction which allows me to do that but I don't remember it.
Yours answers and your time are appreciate.
Best regards.
Florina C.

Hi
The transaction is MN05 or
Logistics->Materials Management->Purchasing->Master Data->Messages->Purchase Order
Max

Settings for Purchase Order output using services for MM-SUS scenario?

Dear Gurus,
I am configuring the service procurement classic and plan driven procurement for MM-SUS
environment. We are on SAP SRM 7.01/ECC 6 EHP5.
I need to maintain the below settings for PO output:
1. RUN transaction SWETYPV
2. IN the object types field, enter CL_SE_PUR_WF_OUT.
3. In the event field, enter CREATED.
4. In the receiver type field, enter WS53800008.
5. In the receiver function module field, enter SWW_WI_CREATE_VIA_EVENT_IBF.
6. Select the 'Linkage Activated' checkbox.
7. Save your entries.
Similarly, one more entry for the event CHANGED.
However, the system is not allowing me to save the settings.
If I choose BOR Object Type 'CL_SE_PUR_WF_OUT', it gives an error message 'Object type CL_SE_PUR_WF_OUT is not defined'.
If I choose object category 'Business class for object type CL_SE_PUR_WF_OUT, it gives an error message 'Class CL_SE_PUR_WF_OUT is not a business class.'
There are similar entries in the table SWETYPV for object type CL_SE_PUR_PO_WF_OUT' with object category CL.If we copy the entries and tries to replace the
object type 'CL_SE_PUR_PO_WF_OUT' with CL_SE_PUR_WF_OUT and save it, it gives an error message 'CL is not used for workflow event'.
Could you please help me on how to configure the settings for PO output from ECC system using services?
Any input is 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

NACE Configuration for Purchase order output "Title Text"

Hello Gurus,
I have a small question, Is it possible to make dynamic Document title when sending purchase order email to vendor.
I have checked configuration in NACE where for each output type where you can maintain "Mail title and Texts". For example if your output type is Email then you can maintain document title text as "Purchase order Email".
Our requirement is to put purchase order name in document title i.e. when vendor receive email in their inbox it says purchase order number.
Please advise.
Thank you
Ritesh

Thanks Jurgen. This note helped us.
Best Regards
Ritesh

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

Update Header Partner data in a Purchase Order in 4.6C system.

Hello all,
I have written a report program to add/update partner data at PO header level.
The report uses BAPI POCHANGE for the update.
But the BAPI_PO_CHANGE does not transfer/update Partner Information for the PO's in 4.6 C system.
The same code functions properly for Purchase Orders in ECC6.0 systems.
Please provide me some inputs for a probable solution to update PO header partner data in 4.6C system.
Thanks in advance.

Hello Hiren,
Thanks for the prompt response.
I am populating the structure POPARTNER with partner information.
And passing header information in POHEADER. i.e the PO Number.
I have not marked any fields in POHEADERX as 'X'. It still works in ECC6 system.
But does not work in 4.6C system.
Thanks in advance.
Edited by: Amar.t on Mar 7, 2010 12:59 PM

Processing log output for Purchase order

Dear All,
Iam getting some problem when iam creating an IDOC and checking in the Processing log for IDOC number.
Actually i had created one custom idoc for Purchase order since my client need only some field and in one line for header and line item, I had done it and i can see it in sdata of EDIDD structure. When i create a Purchase order and save it an idoc number is posting and I can see this file in my physical directory indeed.
Now when iam going into change mode of PO ME22n to see the Processing LOG, It is not showing the IDOC Number in Purchase order output processing log popup.

The processing log will only show output based standard output control (Table NAST).
How is your IDoc being created. Via a user exit, BADI. If so then they will not appear on the processing log.
It is being created as a custom IDOC for which i had written a Z function module and given that in PO processing code which is ME10. When iam checking the standard IDOC for PO it is generating the IDOC in processing log as well.
Iam just placing my code just have a look at it and suggest if any thing needs to be done.
FUNCTION Z_IDOC_OUTPUT_ORDERS.
""Local Interface:
*" IMPORTING
*"     VALUE(OBJECT) LIKE NAST STRUCTURE NAST
*"     VALUE(CONTROL_RECORD_IN) LIKE EDIDC STRUCTURE EDIDC
*" EXPORTING
*"     VALUE(OBJECT_TYPE) LIKE WFAS1-ASGTP
*"     VALUE(CONTROL_RECORD_OUT) LIKE EDIDC STRUCTURE EDIDC
*" TABLES
*"      INT_EDIDD STRUCTURE EDIDD
*" EXCEPTIONS
*"      ERROR_MESSAGE_RECEIVED
*"      DATA_NOT_RELEVANT_FOR_SENDING
DATA: xdruvo.                          "Druckvorgang
DATA: neu VALUE '1',                  "Neudruck
      h_kappl LIKE nast-kappl,         "Hilfsfeld Applikation
      h_parvw LIKE ekpa-parvw,         "Hilfsfeld Partnerrolle
      h_ebeln LIKE ekko-ebeln.         "Hilfsfeld Belegnummer
CLEAR control_record_out.
   xdruvo = neu.
h_kappl = object-kappl.
h_ebeln = object-objky.
h_parvw = object-parvw.
DATA:
       LT_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE,
         L_EDIDC LIKE EDIDC,
         L_SEND_FLAG,
         W_SDATA LIKE EDIDD-SDATA.
DATA: T_BDI_MODEL LIKE BDI_MODEL OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDC LIKE EDIDC OCCURS 0 WITH HEADER LINE.
DATA: T_EDIDD LIKE EDIDD OCCURS 0 WITH HEADER LINE.
DATA: C_MESSAGE_TYPE LIKE EDIDC-MESTYP VALUE 'ZORDER'.
*- Call function module to determine if message is to be distributed
OBJECT_TYPE = 'BUS2012'.
MOVE control_record_in TO control_record_out.
CALL FUNCTION 'ALE_MODEL_DETERMINE_IF_TO_SEND'
    EXPORTING
      MESSAGE_TYPE           = C_MESSAGE_TYPE
    IMPORTING
      IDOC_MUST_BE_SENT      = L_SEND_FLAG.
   EXCEPTIONS
     OWN_SYSTEM_NOT_DEFINED = 1
     OTHERS                 = 2.
DATA : BEGIN OF EKKO_tAB OCCURS 0,
EBELN LIKE EKKO-EBELN,
F1 TYPE C VALUE ',',
BUKRS LIKE EKKO-BUKRS,
F2 TYPE C VALUE ',',
BSART LIKE EKKO-BSART,
F3 TYPE C VALUE ',',
LIFNR LIKE EKKO-LIFNR,
F4 TYPE C VALUE ',',
WAERS LIKE EKKO-WAERS,
F5 TYPE C VALUE ',',
BEDAT LIKE EKKO-BEDAT,
F6 TYPE C VALUE ',',
WERKS LIKE EKPO-WERKS,
F7 TYPE C VALUE ',',
PLIFZ LIKE EKPO-PLIFZ,
F8 TYPE C VALUE ',',
EBELP LIKE EKPO-EBELP,
F9 TYPE C VALUE ',',
MATNR LIKE EKPO-MATNR,
F10 TYPE C VALUE ',',
MENGE LIKE EKPO-MENGE,
F11 TYPE C VALUE ',',
MEINS LIKE EKPO-MEINS,
F12 TYPE C VALUE ',',
END OF EKKO_TAB.
DATA SDATA1 LIKE EKKO_tAB OCCURS 0 WITH HEADER LINE.
DATA EBELN LIKE EKKO-EBELN.
WRITE OBJECT-OBJKY TO EBELN.
SELECT T1EBELN T1BUKRS BSART LIFNR WAERS BEDAT WERKS PLIFZ EBELP MATNR MENGE MEINS
FROM EKKO AS T1
INNER JOIN EKPO AS T2 ON T2EBELN = t1EBELN
INTO CORRESPONDING FIELDS OF TABLE EKKO_tAB
WHERE
*T1~KAPPL = 'EF' AND
T1~EBELN = EBELN.
*T1~KSCHL = 'YEDI' .
DATA SDATA LIKE EDIDD-SDATA.
DATA NDATE LIKE SY-DATUM.
DATA NMENGE(17) TYPE C.
LOOP AT EKKO_tAB.
    WRITE EKKO_TAB-MENGE TO NMENGE.
    NDATE = EKKO_tAB-BEDAT + EKKO_tAB-PLIFZ.
    CONCATENATE EKKO_tAB-EBELP ',' EKKO_tAB-BUKRS ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-LIFNR ',' EKKO_tAB-BEDAT ','
    NDATE ',' EKKO_tAB-BSART EKKO_tAB-EBELN ',' EKKO_tAB-EBELN ', 0,' EKKO_tAB-MATNR ','
    NMENGE ',' EKKO_tAB-MEINS ',' EKKO_tAB-WERKS INTO SDATA.
    MOVE SDATA TO: W_SDATA, T_EDIDD-SDATA.
    MOVE 'ZORDERS' TO T_EDIDD-SEGNAM.
    APPEND T_EDIDD.
ENDLOOP.
*call function 'L_IDOC_SEGMENT_CREATE'
    exporting
         i_segnam = 'ZORDERS'
         i_sdata = w_sdata
    exceptions
         others   = 1.
*LT_EDIDC
call function 'L_IDOC_SEND'
     tables
          t_comm_idoc           = LT_EDIDC
     exceptions
          error_distribute_idoc = 1
          others                = 2.
*DATA T_BDI_MODEL LIKE BDI_MODEL.
WRITE OBJECT-OBJKY TO T_BDI_MODEL.
READ TABLE T_BDI_MODEL INDEX 1.      " maximum 1 recipient
L_EDIDC-DIRECT = 1.
L_EDIDC-DOCNUM = DOCNUM. "***
L_EDIDC-RCVPRN = 'HCM_00_785'.
L_EDIDC-RCVPOR = 'MM_PO_FILO'.
MOVE 'ZORDER'   TO L_EDIDC-MESTYP.
MOVE 'ZPURIDOC' TO L_EDIDC-IDOCTP.
MOVE 'LS'      TO L_EDIDC-RCVPRT.
MOVE T_BDI_MODEL-RCVSYSTEM TO L_EDIDC-RCVPRN.
*MOVE-CORRESPONDING L_EDIDC TO W_EDIDC.
*- Distribute the iDoc
BREAK-POINT.
CALL FUNCTION 'MASTER_IDOC_DISTRIBUTE' "IN UPDATE TASK
    EXPORTING
      MASTER_IDOC_CONTROL            = L_EDIDC
    TABLES
      COMMUNICATION_IDOC_CONTROL     = LT_EDIDC
      MASTER_IDOC_DATA               = T_EDIDD
    EXCEPTIONS
      ERROR_IN_IDOC_CONTROL          = 01
      ERROR_WRITING_IDOC_STATUS      = 02
      ERROR_IN_IDOC_DATA             = 03
      SENDING_LOGICAL_SYSTEM_UNKNOWN = 04.
IF SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
         WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
READ TABLE LT_EDIDC INDEX 1.
control_record_out-direct = '1'.
CONTROL_RECORD_OUT-DOCNUM = DOCNUM. " ***
control_record_out-serial = sy-datum.
control_record_out-serial+8 = sy-uzeit.
control_record_out-mestyp = LT_EDIDC-mestyp.
control_record_out-idoctp = LT_EDIDC-idoctp.
control_record_out-SNDPRN = 'HCM_00_786'.
MOVE 'MM_PO_FILO' TO control_record_out-RCVPOR.
MOVE 'LI'      TO control_record_out-SNDPRT.
MOVE 'SAPQIS' TO control_record_out-SNDPOR.
ENDFUNCTION.

Output Message for Purchase order not being created Automatically

Hi all,
I created a Condition type for Purchase order in MN04 with key combination "Doc.Type/Purch.Org/Vendor". The problem arises when i delete this condition record. After deletion when i create purchase order in me21n for that condition type, the system gives an error.
Message no. 06261 - No message generated for output of purchasing document.
Is there anyway the purchase order message is created automatically again when its condition type has been deleted from MN04.
- Regards
Sahar Khalid

Before creating the entry in MN04 the message was being created automatically. I want the system to create the same output message as it was creating before the creation of the entry in MN04.

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)

Updating Batch classification data from MIGO for Purchase order

Hi,
I need to update batch classification data (in MSC3n) from MIGO for purchase order. The logic needed for this is as below,
1) Pass material and batch to MCH1 table to get CUOBJ_BM.
2) Pass CUOBJ_BM to INOB table to get INOB-OBJEK.
3) Pass INOB-OBJEK to CLAF_CLASSIFICATION_OF_OBJECTS to get class name & characteristic name.
4) Pass INOB-OBJEK, CLASS name and characteristic name to BAPI_OBJCL_CHANGE to update batch classification data.
I created implicit enhancement at the bottom of FM "CLVF_VB_INSERT_CLASSIFICATION". But the problem is, the return parameter of BAPI_OBJCL_CHANGE is giving the following error.
Class type 023, object type MCH1, object RAW-6 0000001151
Object is currently locked by user
The assignment was not changed
Please let me know how to do it. Is there any BADI or User Exit?

Hi,
As you said the break point is not triggering did you activate your exit and activated even the project to which your exit is assigned.
I hope you missed activating your project in CMOD transaction. Please verify it once and if it is not activated then immediately activate it and try debugging again.
Regards,
Rafi

Message Output for purchase order

Dear SAP Expert,
We have defined the message output type for purchase order document type XX with special function. We have maintained condition record for the same. It is working fine.
Now we have defined another output type for another PO document type YYwith special function by copying earlier one.
But message output is not genarated in case of YY document type.
Please tell us what we have missed out.
Thanks & Regards,
Reva.

Hi Reva,
In ME22N for your PO, click on the Messages button. Then click on the blue information button - this should display the output determination analysis for the order, and will show you which output determination procedure was used, which output type and access sequence was processed and whether the system was able to find a matching record. At the lowest level of detail it will show you the keys that were used to read the condition records. All this information should help you to determine why a condition record could not be found for the purchase order.
Regards,
Monika

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

Reg.Output type for purchase order

Dear Sir
I followed your steps but not come to "List of allowed output"
when I select the message for Purchase order(ME21N). There are listing NEU,SPO,MAHN and AUFB.
I just copy the NEU and all,I did not change anything.
Maintain 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
Ex:
EF---> TES
Select TES and double click on Mail title and texts and go to
EN- New Purchase Order Print Out,
Select TES again and double click on Processing routines,
Select TES again and double click on Partner Roles
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 TES.
Please help me sir
Rajj

Hi
Go to NACE
Select application as EF Purchase Order
Define TES as out put type there
Vishal...

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

Different interfaces for purchase order output from MM system

Similar Messages

Maybe you are looking for