Required fields for Purchase Order through ORDERS05 idoc

Hi,
I'm creating PURCHASE orders from ORDERS05 IDOC through XI. Could anyone tell me what all segments and fields are required for this purpose, if they have done this earlier.
Regards,
Vijay

Hi Vijay,
It depends how the input is populated. Anyway to know about Mandatory Segment /Fields, you can go to Transaction code WE30 in the R/3 system and give the idoc name and open the structure. There you can get to know about Mandatory Segments/fields etc with the help of Occurences
Regards,
Moorthy

Similar Messages

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.

Need a field for purchase order quantity

We need a field that is fixed once the PO is created and is never updated even if the qty is changed later on.

Hi Chandra
Not clear with your query...
Are you looking for a field to act as a constant where you can store the PO Item Quantity which was initially created???
If so, not really sure on the reason but you can get the orginal qty value from Change Documents.
OBJECTID for Purchase Orders is <b>EINKBELEG</b>.
Kind Regards
Eswar

How to Send Purchase Order through EDI/IDOC.

Hi Experts,
We are using SAP ECC.5. And intending to send the Purchase Order to Supplier through EDI/IDOC and Receive the Inbound Acknowledgement.
Appreciate, if you could help me, the required Configuration details for outbound and inbound (PO & Acknowledgement).
Reg
Kumar

Hi Kiran
Many thanks for the response. It is true that by changing the message type to EDI can generate idoc. What is not clear is any other config we need to do interms of Message generation, Resubmitting failed IDOC etc..
Out requirement is that we would generate the IDOC for New and changed docs and send to external EDI converter.
Inbound, receive the IDoc and post the acknowledgement.
Appreciate, if you could forward any document link which can explain the details.
Reg
Kumar

Expand Table Control with Fields for Purchase Order Item Overview

Hi Gurus.
Hereu2019s something easy for you, I hope/ think. We just want to additionally show the field u201CMFRPNu201D in the purchase order item overview. See structure MEPO1211 for the table control.
How can we do this? Is it possible without a modification? Is there anything to pay attention to?
Lot's of questions, because we donu2019t find any complete solutions yet. It seems there are no official SAP suggestions for this issue.
Thanks in advance!
Regards
Patric

Is there no one out there who can answer my question?

Required BADI for purchase order

Hi experts,
Can any one please suggest me which BADI or userexit suitable in purchase order to restrict accountassignement category depend upon Doc type with the suitable method.

Hi Ram,
Actually my requirement is like this .
In the me21n tcode, if doctype of purchase order is 'ZCAP' then it has to allow the accasscategory 'A' only.
If any other accasscategory assigned then it has to display error message.
For that i have gone for me_process_po_cust BADI. But it does not had any changing parameters to satisfy my requirements.
Is there any alternative?
pleae Reply me asap .
Its very urgent...

Requirement Urgency for Purchase order

Hi,
I have configured Requirement Urgency ( I have created 2 code "01 and 99 respectively for emergency and routine , now while creating PR, system proposes 99 as routine , which is correct as per my requirement, again when I do change the requirement priority in PR , it is allowing me to so ( e.g. from 99 to 01 ) and based on that I am able to get the report in ME5A.
However , when I am creating P.O with reference to PR, I am able to see the only "99 " codes no "01, codes.?
Is any clue ? can any body suggest.
Thanks & Regards
Sudhansu

Hi,
The configuration and impact attached here with for your reference, if you can provide any idea.
STEP 1 :ACTIVATE REQUIREMENT PRIORITIZATION
STEP 2 : DEFINE REQUIREMENT URGENCY GROUP
STEP 3 : DEFINE AND ASSIGN REQUIREMENT URGENCY
STEP 4 : PURCHASE REQUISITION
STEP 5 : PURCHASE ORDER
Thanks & Regards
Sudhansu

Regarding fields for Purchase order

can any body help what are the fields reqiured to develop a p.o report to display the change date,user name,time,p.o name and vendor code.

Hi
see the sample report for the fieldnames and other logic
all the PO info is there here.
*& Report ZMM_PO_REPORT
REPORT ZMM_PO_REPORT message-Id yb
       NO STANDARD PAGE HEADING
       LINE-COUNT 60(1)
       LINE-SIZE 230.
       D A T A B A S E T A B L E S   D E C L A R A T I O N
TABLES: lfa1,           " Vendor Master
        t161,           " PO Doc Types
        t024,           " Purchase Groups
        ekko.           " PO Header
               T Y P E S D E C L A R A T I O N S
Purchase Orders Main Structure
TYPES: BEGIN OF s_po,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bukrs TYPE bukrs,           " Company Code
        bsart TYPE bbsrt,           " PO Type
        lifnr TYPE lifnr,           " Vendor No
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
       END OF s_po.
Purchase Orders History Structure
TYPES: BEGIN OF s_account,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        gjahr TYPE mjahr,           " Fiscal Year
        belnr TYPE mblnr,           " PO Invoice No
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Local Currency
        dmbtr TYPE dmbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
        shkzg TYPE shkzg,           " Dr/Cr Indicator
       END OF s_account.
Purchase Orders History Structure(Item Sum)
TYPES: BEGIN OF s_inv_sum,
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        menge TYPE menge_d,         " PR Quantity
        wrbtr TYPE wrbtr,           " Price in Foreign Currency
        waers TYPE waers,           " Currency
       END OF s_inv_sum.
Purchase Orders Main Structure
TYPES: BEGIN OF s_rep,
        lifnr TYPE lifnr,           " Vendor No
        ebeln TYPE ebeln,           " PO No.
        ebelp TYPE ebelp,           " PO Item
        bstyp TYPE bstyp,           " PO Category
        bsart TYPE bbsrt,           " PO Type
        ekgrp TYPE bkgrp,           " Purchase Group
        waers TYPE waers,           " Currency
        bedat TYPE etbdt,           " PO Date
        txz01 TYPE txz01,           " Material Text
        werks TYPE ewerk,           " Plant
        lgort TYPE lgort_d,         " Storage Location
        matkl TYPE matkl,           " Material Group
        menge TYPE bamng,           " PR Quantity
        meins TYPE bamei,           " UOM
        bprme TYPE bbprm,           " Price Unit
        netpr TYPE netpr,           " Net price
        peinh TYPE peinh,           " Price Unit UOM
        pstyp TYPE pstyp,           " Item Category
        knttp TYPE knttp,           " Account Assignment Category
        name1 TYPE name1,           " Plant
        orewr TYPE netpr,           " To be Invoiced Price
        curr TYPE waers,           " Inv Doc Currency
       END OF s_rep.
           D A T A D E C L A R A T I O N S
DATA: gv_title1 TYPE sylisel,            " Report title
      gv_dial.                           " Color flag
            C O N S T A N T S D E C L A R A T I O N S
CONSTANTS: c_x                VALUE 'X',   " Flag X
           c_h                VALUE 'H',   " Debit
           c_vgabe TYPE vgabe VALUE '2'.   " Transaction Type
     I N T E R N A L T A B L E S D E C L A R A T I O N S
DATA: i_po    TYPE STANDARD TABLE OF s_po WITH HEADER LINE,
                             " Purchase Order
      i_inv   TYPE STANDARD TABLE OF s_inv_sum WITH HEADER LINE,
                                     " PO Invoice Values
      i_rep   TYPE STANDARD TABLE OF s_rep WITH HEADER LINE,
                                 " PO Invoice Values
      i_ekbe TYPE STANDARD TABLE OF s_account WITH HEADER LINE.
                           " PO Invoice Values
                 S E L E C T I O N S C R E E N                      *
SELECTION-SCREEN BEGIN OF BLOCK b1 WITH FRAME TITLE text-001.
SELECT-OPTIONS: s_lifnr FOR lfa1-lifnr MATCHCODE OBJECT kred,
                s_ebeln FOR ekko-ebeln MATCHCODE OBJECT mekk,
                s_bsart FOR t161-bsart,
                s_ekgrp FOR t024-ekgrp,
                s_bedat FOR ekko-bedat.
SELECTION-SCREEN END OF BLOCK b1.
                  I N I T I A L I Z A T I O N                        *
INITIALIZATION.
              A T S E L E C T I O N - S C R E E N                   *
AT SELECTION-SCREEN.
Validate the screen fields
PERFORM validate_screen.
               S T A R T - O F - S E L E C T I O N                   *
START-OF-SELECTION.
Fetch main data
PERFORM fetch_data.
               T O P - O F - P A G E                                 *
TOP-OF-PAGE.
Header of the List
PERFORM header.
               E N D - O F - P A G E                                 *
Footer
END-OF-PAGE.
ULINE.
               E N D - O F - S E L E C T I O N                       *
END-OF-SELECTION.
Display the Report Output data
PERFORM display_data.
At Line-Selection
AT LINE-SELECTION.
When double clicked on EBELN display the details of Purchase Doc
PERFORM line_sel.
*&      Form validate_screen
Validation of Selection Screen fields
FORM validate_screen .
Validation of Vendor Number
CLEAR lfa1-lifnr.
IF NOT s_lifnr[] IS INITIAL.
    SELECT lifnr UP TO 1 ROWS
        INTO lfa1-lifnr
        FROM lfa1
        WHERE lifnr IN s_lifnr.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Vendor'(002).
    ENDIF.
ENDIF.
Validation of PO Number
CLEAR ekko-ebeln.
IF NOT s_ebeln[] IS INITIAL.
    SELECT ebeln UP TO 1 ROWS
        INTO ekko-ebeln
        FROM ekko
        WHERE ebeln IN s_ebeln.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Document Number'(003).
    ENDIF.
ENDIF.
Validation of PO Document Type
CLEAR t161-bsart.
IF NOT s_bsart[] IS INITIAL.
    SELECT bsart UP TO 1 ROWS
        INTO t161-bsart
        FROM t161
        WHERE bsart IN s_bsart.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchase Document Type'(004).
    ENDIF.
ENDIF.
Validation of Purchasing Group
CLEAR t024-ekgrp.
IF NOT s_ekgrp[] IS INITIAL.
    SELECT ekgrp UP TO 1 ROWS
        INTO t024-ekgrp
        FROM t024
        WHERE ekgrp IN s_ekgrp.
    ENDSELECT.
    IF sy-subrc <> 0.
      MESSAGE e000 WITH 'Invalid Purchasing Group'(005).
    ENDIF.
ENDIF.
ENDFORM.                    " validate_screen
*&      Form fetch_data
Fetching the PO related data from Database Tables
FORM fetch_data .
CLEAR i_po.
REFRESH i_po.
SELECT a~ebeln            " PO No.
         b~ebelp            " PO Item
         a~bstyp            " PO Category
         a~bukrs            " Company Code
         a~bsart            " PO Type
         a~lifnr            " Vendor No
         a~ekgrp            " Purchase Group
         a~waers            " Currency
         a~bedat            " PO Date
         b~txz01            " Material Text
         b~werks            " Plant
         b~lgort            " Storage Location
         b~matkl            " Material Group
         b~menge            " PR Quantity
         b~meins            " UOM
         b~bprme            " Price Unit
         b~netpr            " Net price
         b~peinh            " Price Unit UOM
         b~pstyp            " Item Category
         b~knttp            " Account Assignment Category
    INTO TABLE i_po
    FROM ekko AS a JOIN ekpo AS b
    ON a~ebeln = b~ebeln
    WHERE a~ebeln IN s_ebeln AND
          a~lifnr IN s_lifnr AND
          a~ekgrp IN s_ekgrp AND
          a~bsart IN s_bsart AND
          a~bedat IN s_bedat.
SORT i_po BY ebeln ebelp.
break-point.
IF NOT i_po[] IS INITIAL.
Fetch the PO History/Invoice Details from EKBE Table
    CLEAR i_ekbe.
    REFRESH i_ekbe.
    SELECT ebeln           " PO No.
           ebelp           " PO Item
           gjahr           " Fiscal Year
           belnr           " PO Invoice No
           menge           " PR Quantity
           wrbtr           " Price in Local Currency
           dmbtr           " Price in Foreign Currency
           waers           " Currency
           shkzg           " Dr/Cr Indicator
     INTO TABLE i_ekbe
     FROM ekbe
     FOR ALL ENTRIES IN i_po
     WHERE ebeln = i_po-ebeln AND
           ebelp = i_po-ebelp AND
           vgabe = c_vgabe.
    IF sy-subrc = 0.
      SORT i_ekbe BY ebeln ebelp.
      LOOP AT i_ekbe.
        IF i_ekbe-shkzg = c_h.
          i_ekbe-wrbtr = i_ekbe-wrbtr * -1.
        ENDIF.
        MODIFY i_ekbe.
      ENDLOOP.
break-point.
Sum up the Item wise Invoice totals
      LOOP AT i_ekbe.
        AT END OF ebelp.
          READ TABLE i_ekbe INDEX sy-tabix.
          SUM.
          MOVE-CORRESPONDING i_ekbe TO i_inv.
          APPEND i_inv.
        ENDAT.
        CLEAR i_inv.
      ENDLOOP.
      SORT i_inv BY ebeln ebelp.
        break-point.
    ENDIF.
ENDIF.
Move the Vendor Name and Invoice Values to I_rep Internal Table
LOOP AT i_po.
    MOVE-CORRESPONDING i_po TO i_rep.
    CLEAR i_inv.
    READ TABLE i_inv WITH KEY ebeln = i_po-ebeln
                              ebelp = i_po-ebelp.
    IF sy-subrc = 0.
      i_rep-orewr = ( i_po-menge - i_inv-menge ) * i_po-netpr.
      i_rep-curr = i_inv-waers.
    ELSE.
      i_rep-orewr = i_po-menge * i_po-netpr.
      i_rep-curr = i_po-waers.
    ENDIF.
break-point.
Get the Vendor Name
    CLEAR lfa1-name1.
    SELECT SINGLE name1 FROM lfa1 INTO lfa1-name1
      WHERE lifnr = i_po-lifnr.
    IF sy-subrc = 0.
      i_rep-name1 = lfa1-name1.
    ENDIF.
    APPEND i_rep.
    CLEAR i_rep.
      break-point.
ENDLOOP.
SORT i_rep BY lifnr ebeln ebelp.
DELETE i_rep WHERE orewr LE 0.
break-point.
ENDFORM.                    " fetch_data
*&      Form display_data
Display the Report Output data
FORM display_data .
DATA: lv_flag,               " New Flag
        lv_rec TYPE i.         " No of Records
CLEAR lv_rec.
IF i_rep[] IS INITIAL.
    MESSAGE e000 WITH 'No Data found'(022).
ELSE.
    LOOP AT i_rep.
Toggle Color
      PERFORM toggle_color.
      IF lv_flag <> space.
        NEW-LINE.
      ENDIF.
At New Purchase Document
      AT NEW ebeln.
        WRITE:/1 sy-vline, 2(10) i_rep-ebeln INTENSIFIED OFF.
        lv_flag = c_x.
        lv_rec = lv_rec + 1.
      ENDAT.
      WRITE: 1 sy-vline,
            12 sy-vline,13(4)   i_rep-bsart,
            17 sy-vline,18(10) i_rep-lifnr,
            28 sy-vline,29(35) i_rep-name1,
            64 sy-vline,65(4)   i_rep-ekgrp,
            69 sy-vline,70(10) i_rep-bedat,
            80 sy-vline,81(5)   i_rep-ebelp,
            86 sy-vline,87(40) i_rep-txz01,
           127 sy-vline,128(9) i_rep-matkl,
           137 sy-vline,138(1) i_rep-pstyp,
           139 sy-vline,140(1) i_rep-knttp,
           141 sy-vline,142(4) i_rep-werks,
           146 sy-vline,147(4) i_rep-lgort,
           151 sy-vline,152(13) i_rep-menge UNIT i_rep-meins,
           165 sy-vline,166(3) i_rep-meins,
           169 sy-vline,170(15) i_rep-netpr CURRENCY i_rep-waers,
           185 sy-vline,186(4) i_rep-waers,
           190 sy-vline,191(5) i_rep-peinh,
           196 sy-vline,197(4) i_rep-bprme,
           201 sy-vline,202(15) i_rep-orewr CURRENCY i_rep-curr,
           217 sy-vline,218(4) i_rep-curr,
           222 sy-vline,223(7) i_rep-bstyp centered,
           230 sy-vline.
      NEW-LINE.
      hide: i_rep-ebeln.
    ENDLOOP.
    ULINE.
    FORMAT COLOR OFF.
    WRITE : /2 'Total Number of Purchasing Documents:'(025) COLOR 3,
                lv_rec COLOR 3.
ENDIF.
ENDFORM.                    " display_data
*&      Form header
Write the Report Header
FORM header .
FORMAT RESET.
header
WRITE:/1(230) 'LIST OF PURCHASE DOCUMENTS PER VENDOR'(006) CENTERED.
SKIP.
FORMAT COLOR COL_HEADING.
ULINE.
WRITE:/1 sy-vline,2(10)   'Pur.Doc.No'(006) CENTERED,
        12 sy-vline,13(4)   'Type'(007),
        17 sy-vline,18(10) 'Vendor'(008) CENTERED,
        28 sy-vline,29(35) 'Name'(009) CENTERED,
        64 sy-vline,65(4)   'PGrp'(010) CENTERED,
        69 sy-vline,70(10) 'Doc.Date'(012) CENTERED,
        80 sy-vline,81(5)   'Item'(011),
        86 sy-vline,87(40) 'Material Short Text'(024) CENTERED,
       127 sy-vline,128(9) 'Mat.Group'(013),
       137 sy-vline,138(1) 'I',
       139 sy-vline,140(1) 'A',
       141 sy-vline,142(4) 'Plnt'(014),
       146 sy-vline,147(4) 'SLoc'(015),
       151 sy-vline,152(13) 'Quantity'(016) CENTERED,
       165 sy-vline,166(3) 'UoM'(017),
       169 sy-vline,170(15) 'Net Value'(018) CENTERED,
       185 sy-vline,186(4) 'Curr'(019),
       190 sy-vline,191(5) 'Per'(020),
       196 sy-vline,197(4) 'Unit'(021),
       201 sy-vline,202(15) 'To be Invoiced'(023) CENTERED,
       217 sy-vline,218(4) 'Curr'(019),
       222 sy-vline,223(7) 'Doc.Cat'(026),
       230 sy-vline.
ULINE.
ENDFORM.                    " header
*&      Form toggle_color
This routine alters the color of the records in the list
FORM toggle_color.
IF gv_dial = space.
    FORMAT COLOR COL_NORMAL INTENSIFIED OFF.
    gv_dial = c_x.
ELSE.
    FORMAT COLOR 1 INTENSIFIED OFF.
    CLEAR gv_dial.
ENDIF.
ENDFORM.                    " toggle_color
*&      Form LINE_SEL
*When double clicked on EBELN field display the details of Purchase Doc
FORM line_sel.
CASE sy-lsind.
    WHEN '1'.
      DATA: lv_field(20),
            lv_value(10),
            lv_bstyp like i_rep-bstyp.
      clear: lv_bstyp,lv_value, lv_field.
      GET CURSOR FIELD lv_field VALUE lv_value.
      IF lv_field = 'I_REP-EBELN'.
        IF NOT lv_value IS INITIAL.
          READ LINE sy-index FIELD VALUE i_rep-bstyp
                                   INTO lv_bstyp.
         READ CURRENT LINE FIELD VALUE i_rep-bstyp INTO lv_bstyp.
          if lv_bstyp = 'F'.
            SET PARAMETER ID 'BES' FIELD lv_value.
            CALL TRANSACTION 'ME23N' AND SKIP FIRST SCREEN.
          elseif ( lv_bstyp = 'K' or lv_bstyp = 'L' ).
            SET PARAMETER ID 'VRT' FIELD lv_value.
            CALL TRANSACTION 'ME33' AND SKIP FIRST SCREEN.
          elseif lv_bstyp = 'A'.
            SET PARAMETER ID 'ANF' FIELD lv_value.
            CALL TRANSACTION 'ME43' AND SKIP FIRST SCREEN.
          endif.
        ENDIF.
      ENDIF.
ENDCASE.
ENDFORM.                    " line_sel
Regards
Anji

Long text field for Purchase Order help

Hey guys,
First, I'm VERY new to ABAP/SRM in general. So please be patient with me.
We have users who are entering additional text comments into SRM (when creating a new PO).
The problem is...when they enter the text and hit <ENTER> I am getting it on the SCC side as "#" seperating the lines.
For example...
User types
line 1
line 2
line 3
It is appearing as line 1#line 2#line 3
I've done some debugging, and found the filed it is referring to:
IS_OBJECT-SC-LONGTEXT and the field is TDLINE
But I have no idea how to fix this...is this something I can change? We don't want to change SAP code...is there a BADI I can access??? Anything?

Hello,
To look for SAP OSS notes, you need a user and his password to access to SAP website:
[http://service.sap.com/support]
If you don't have it, ask for your team leader to give you one.
Regards.
Laurent.

Idoc for purchasing order

can any1 explain the steps needed to send a purchase order through ALE/IDOCS
pls explain it with reference to PURCHASE ORDER

Hi,
cehck the same...
This method is used for distributing transaction data like purchase order, sales order etc.
In this method the extra transaction code that we use is we41 (outbound process code) and we use this in the message control tab in the partner profiles.
The transaction codes that are required for this method are
We81
We30
We31
We82
We21
We20
Bd64
Nace
Me22n (purchase order), va02 (sales order) etc.
Ex: purchase order.
Message type: ORDERS
Idoc type: ORDERS05
Outbound process code for purchase order: me10
The steps that are to be followed are:
Check for the message type in the transaction in we81.
check for the idoc type in the transaction we30.
check we82 in which the link between message type and idoc type is there.
create the port in we21.
Configure the partner profiles in we20.
Click on the + button outbound parameters and give the message type, receiver port
Idoc type.
Now press on the message control tab, this is the place where u give the outbound process code. The message type in the message control is the output type that is used in the nace transaction.
Create a distribution model in bd64.
Go to purchase order transaction (me22n).and press the messages tab
In the messages tab give the output type and the distribution medium as distribution-ale and then save it.
Reward if helpful.
Regards,
Nagaraj

Generating idoc for Purchase orders - ORDERS05

Hi,
Can you please let me know how to generate idoc for Purchase orders - ORDERS05-manually, not by activating change pointers.

hi
i believe u wont have this functionality as it is a transcational data and the one way of doing it by configuring output types only.

IDOC for purchase order

Hi,
I created an IDOC using the basic type orders04 , i populated all the required fields and tried to run the idoc through WE20 .The idoc got generated but with an error saying "Purchasing document & does not exist"..I am not able to see which part of the segment this error is getting popped up.Please help me.
Thanks & Regards
Abhishek

Hi Abhishek,
In your header you suggest that you want to create a purchase order using ORDERS04; however this message can't be used to create purchase orders. You should use message PORDCR instead.
In case you do want to create a sales order, you could set a break point in function module IDOC_INPUT_ORDERS at the call of transaction VA01, switch MODE to 'A' and the sales order is created in dialog mode. Perhaps you might then find out what the cause of the error is.
Hope this is of any help.
Regards,
John.

How to implement Change pointers for Purchase order - ME22N - Custom Fields

Hi Experts,
Can you please tell me how to implement - Change Pointer for Custom fields in IDOC.
I am working on IDOC - For purchase order - acknowledgements - in custom screen/tab in ME22N.
Everything is working fine according to my requirement.
All i need to know is the process of - Creating/Change - Change pointers for Custom fields.
1.How to implement change pointers for custom fields.
2.Can we maintain - Change Document - for custom fields at data element level?
P.S. - I have browsed many previous - forums before posting a new discussion.
please share your inputs...
explaining how to create/implement - change pointers for custom fields will help me .
Regards,
Karthik Rali.

Hi,
To maintain Change Document for custom field:
1. Check if "Change document" checkbox is set in data element.
2. Find Change Document Object for transaction.
   You can use SQL trace - ST05.
   Look there for line with table CDHDR and statement insert values
   (for example for transaction KA02 Change Document Object is KSTAR)
3. Regenerate update program for this Change Document Object in transaction SCDO
Change documents for z-fields schould be generated.
I am not sure about change pointers but they are configured somehow in BD61 and BD50.

Standard Idoc for Purchase order?

Hi,
Can you please let me know what is the Standard Idoc for Purchase order?
POINTS WILL BE AWARDED

Hi Guest
You can use it, if all your required field are in that Idoc basic type.
http://sap.ittoolbox.com/documents/popular-q-and-a/extending-a-basic-idoc-type-2358
http://abapprogramming.blogspot.com/2007/11/abap-idocs-basic-tools.html
Award points for helpful answers

Issue with ALE configuration for creating the idoc for Purchase orders

Hello,
I am trying to send the purchase order through message type configuration using ALE.
I am using idoc ORDERS05, message ORDERS, Process Code in Partner profile ME10.
In NACE transaction for the Application EF, Output Type NEU the ALE Configuration is done for Program RSNASTED Form ALE_PROCESSING.
I have done ALE distribution using BD64.
Now the problem is that when an order is created or changed in the message output of the PO I am seeing the status as yellow i.e.not processed.
In NAST table, the entry is there but on executing RSNAST00 nothing happens.
Please provide me the pointers to solve the given problem.
Regards,
Mayank

Hi,
Guess it looks like the output is getting proposed but its not getting processed. Check the output type configuration. Check the TIme Settings in the output type configuration.
It is possible to set the Time when the output must be processed. Is it on SAVE or is it set to other settings. If its set to via background job then the background job must be run to process the output types.
Check and let me know if all is fine at the output type configuration.
Cheers
VJ

Required fields for Purchase Order through ORDERS05 idoc

Similar Messages

Maybe you are looking for