Determine classname & classtype for Purchase Order?

Hi All
I'm completely new to SAP, apologies in advance.
So I'm trying to create a external document url against a purchase order via a BAPI.
Looking at this thread [FM to create external document(URL)|FM to create external document(URL)]  BDS_BUSINESSDOCUMENT_CRE_O_URL is the one to use.
First question: is that correct?
The BAPI takes as inputs CLASSNAME and CLASSTYPE which Im assuming are used to identify that this is being attached to, in this case, a PO.
Second question: Is that correct and if so how do I find out what these values are for a Purcahse Order and other objects in SAP?
thanks

Hi Jonnoking,
1) Function module u201CBDS_BUSINESSDOCUMENT_CRE_O_URLu201D is correct to u201CCreate External Document (URL)u201D
2) To find u201CCLASS NAMEu201D & u201CCLASS TYPEu201D values for Purchase Order or any other objects below are the transaction codes where it is maintained:
a) Transaction Code : SBDSV1 - Maintenance View for BDS_LOCL Transparent Table
b) Transaction Code : SBDSV2 - Maintenance View for BDS_CL_DOC Transparent Table (Here you can search the CLASS NAME & CLASS TYPE with the help of DOC_TYPE like u201CMEOORDERu201D for purchase order & other needful objects like INVOICES)
c) Transaction Code : SBDSV3 - Maintenance transaction for V_BDS_CL View (Itu2019s a view of tables - BDS_CLASS & BDS_CLASSL)
3) Transparent Table References:
a) BDS_LOCL  - BDS: Assignment of Application Classes to KPro Doc. Classes
b) BDS_CL_DOC - BDS: Class Definition
c) BDS_CLASS -  BDS: Class Definition
d) BDS_CLASSL - BDS: Language Table for Class Definition
Please find below link for your further reference :
http://www.architectsap.com/blog/sap/sap-bds-business-document-service-for-storage-of-documents-and-attachments-in-sap-ecc/
Best Regards.
Sudhanshu Garg

Similar Messages

  • 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

  • Output determination for purchase order

    Dear friends,
    Please help me, how to create condition record for both printout and email for output determination of standard PO.
    I have created condition record through MN04 for Purchase order with medium(external send) and it worked.
    I also need to create condition record for printout. Because Client wants to select either email,fax or printout. They will select whatever sending option.when i tried to create condition record for medium(1-printout).I got an error " The condition record entered already exists". So i tried to change that condition record,but i got here also error as "The condition is being processed in the current session".
    Please help me to set up condition record for both mail and printout for standard PO.
    Thanks

    For this kind of option you need diff message type like
    use NEU for Fax and Print and for Email create new message type than it will work.

  • Determine Plant and Sloc for Purchase Order Creation

    Hi Gurus,
    I want to determine while create a Purchase Order (ME21N), I can restrict the Purchase Order only for specific Order Type , specific Plant and specific Storage Location.
    The business needs is to prevent human error while create Purchase Order with wrong Order Type, Plant and SLoc combination.
    Is there any Exit related ?
    Thx in advance.
    Tri W

    Hi ,
    This is MM question
    In MM , you could use authorzation in PFCG to limit the plant selection and document typefor a specific  user .
    This would also have effection to the ME21N .
    For the storage location ,then please to set the field as display only and then add a default value to the user in
    the personal setting.
    I hope this will help you a little bit apart from the  BADI.
    Regards
    Summer Wang

  • SAP how to determine the account in Goods receipt for purchase order?

    We know when we make a Goods receipt for purchase order,we will use the account in GBB and BSX define in OBYC. But where can we find the rule? I mean why system can find the account in GBB and BSX , not the other TEcode?

    HI
    This is again based on the movement type which SAP has created a link internally.
    So if you see when a document is posted it basically derives the GL accounts based on the Movement type,Valuation class,valaution area and so on.
    Good luck
    Hari

  • Profit center for purchase order without account assignment

    I've requirement to include profit centers in purchase orders without account assignment category.
    The trouble is when there is no profit center maintained in material master.
    Is there a way to determine profit center in purchase order for such cases?

    Dear Abinash,
    Define substitution in GGB1 at line item level as shown below:
    Prerequisite : BSEG-WERKS = Maintain plant
    Substitution : BSEG-PRCTR = maintain profit centre as constant value
    After define it, assign to the co.code.
    Regards,
    Mukthar

  • 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)

  • User Exit for Purchase Order Release Strategy

    Hi,
    I am a little new to this, how do I search for a user exit for purchase order release strategy (TCode ME29N).
    Thanks in advance.
    Mick

    Hi
    Check the following Exits and BADI for Pur Requisition
    Enhancement
    MEVME001 WE default quantity calc. and over/ underdelivery tolerance
    MM06E001 User exits for EDI inbound and outbound purchasing documents
    MM06E003 Number range and document number
    MM06E004 Control import data screens in purchase order
    MM06E005 Customer fields in purchasing document
    MM06E007 Change document for requisitions upon conversion into PO
    MM06E008 Monitoring of contr. target value in case of release orders
    MM06E009 Relevant texts for "Texts exist" indicator
    MM06E010 Field selection for vendor address
    MM06E011 Activate PReq Block
    MMAL0001 ALE source list distribution: Outbound processing
    MMAL0002 ALE source list distribution: Inbound processing
    MMAL0003 ALE purcasing info record distribution: Outbound processing
    MMAL0004 ALE purchasing info record distribution: Inbound processing
    MMDA0001 Default delivery addresses
    MMFAB001 User exit for generation of release order
    MRFLB001 Control Items for Contract Release Order
    AMPL0001 User subscreen for additional data on AMPL
    LMEDR001 Enhancements to print program
    LMELA002 Adopt batch no. from shipping notification when posting a GR
    LMELA010 Inbound shipping notification: Transfer item data from IDOC
    LMEQR001 User exit for source determination
    LMEXF001 Conditions in Purchasing Documents Without Invoice Receipt
    LWSUS001 Customer-Specific Source Determination in Retail
    M06B0001 Role determination for purchase requisition release
    M06B0002 Changes to comm. structure for purchase requisition release
    M06B0003 Number range and document number
    MEQUERY1 Enhancement to Document Overview ME21N/ME51N
    MELAB001 Gen. forecast delivery schedules: Transfer schedule implem.
    MEFLD004 Determine earliest delivery date f. check w. GR (only PO)
    MEETA001 Define schedule line type (backlog, immed. req., preview)
    ME590001 Grouping of requsitions for PO split in ME59
    M06E0005 Role determination for release of purchasing documents
    M06E0004 Changes to communication structure for release purch. doc.
    M06B0005 Changes to comm. structure for overall release of requisn.
    M06B0004 Number range and document number
    Business Add-in
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Custome
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_PURCHDOC_POSTED Purchasing Document Posted
    SMOD_MRFLB001 Control Items for Contract Release Order
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_REQ_POSTED Purchase Requisition Posted
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_BSART_DET Change document type for automatically generated POs
    ME_BAPI_PR_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PO_CREATE_01
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMITMENT_RETURN Commitment for return item
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CHECK_OA Check BAdI for Contracts
    Reward points if useful
    Rgds,
    Naren

  • User-Exit message for Purchase Order

    Hello,
    I've implemented a specific type of message (ZNEU) for purchase order.
    With some specifics conditions (not managed in SPRO), I'd like that the ouput message of a purchase order is either the standard one NEU or my specific ZNEU..but noth both as actually.
    Is there any user-exit where I can code and change the ouput message determination  ?
    Thanks a lot in advance.
    Best regards
    Fanny PONEL ( GROUX).

    No user exit for this but this can be control by MN04.
    Here you can control the ouyput type trigger
    youmay need to configure the access seq and maintian that for your ZNEU conditon.

  • User Exit/BADI for Purchase Order and Purchase Requisitions

    HI,
    I have a requireent where i have to check the the user does not enter both Subitems and Over a Limit for a Service Purchase Requisition.
    Is there a User Exit or Badi that i can use where this information is availaible.
    also i have to check that release strategy is assigned to every purchase order where the version has been completed.
    Is there a User Exit or Badi where Information of EREV table is availaible.
    Regards,
    Tarun Bahal

    For Purchachase requisition , the BADIs and USER EXITS are
    ME_COMMITMNT_PARKING BAdI for Redefining Commitment Interface When Parking
    ME_MEREQ_PARKING BAdI Purchase Requisition: "Hold"
    ME_REQ_HEADER_TEXT Copy Header Text: Enjoy Purchase Requisition
    try with the above BADI's
    MEREQ001 Customers' Own Data in Purchase Requisition
    for Purchase order , the BADIs and USER EXITS are
    ARC_MM_EKKO_CHECK BAdI: Enhancement of Archivability Check (MM_EKKO)
    ARC_MM_EKKO_WRITE BAdI: Enhancement of Scope of Archiving (MM_EKKO)
    EXTENSION_US_TAXES Extended Tax Calculation with Additional Data
    MEGUI_LAYOUT BAdI for Enjoy Purchasing GUI
    ME_ACTV_CANCEL_PO BAdI for Activating the Cancel Function at Header Level
    ME_BADI_DISPLAY_DOC BAdI for Internal Control of Transaction to be Invoked
    ME_BAPI_PO_CREATE_01
    ME_BAPI_PO_CREATE_02
    ME_BAPI_PR_CREATE_01
    ME_BAPI_PR_CREATE_02
    ME_BSART_DET Change document type for automatically generated POs
    ME_CCP_ACTIVE_CHECK BAdI to check whether CCP process is active
    ME_CCP_BESWK_AUTH_CH BAdI for authorization checks for procuring plant
    ME_CCP_DEL_DURATION Calc. of Delivery Duration in CCP Process (Not in Standard)
    ME_CHANGE_CHARACTER Customer-Specific Characteristics for Product Allocation
    ME_CHANGE_OUTTAB Enrich ALV Output Table in Purchasing
    ME_CHECK_ALL_ITEMS Run Through Items Again in the Event of Changes in EKKO
    ME_CHECK_OA Check BAdI for Contracts
    ME_CHECK_SOURCES Additional Checks in Source Determination/Checking
    ME_CIN_LEINRF2R BADI for CIN India - Delivery charges
    ME_CIN_LEINRF2V BADI for LEINRF03 excise_invoice_details
    ME_CIN_MM06EFKO Copy PO data for use by Country version India
    ME_CIP_ALLOW_CHANGE Configuration in Purchasing: Changeability Control
    ME_CIP_REF_CHAR Enables Reference Characteristics in Purchasing
    ME_COMMITMENT_RETURN Commitment for return item
    ME_COMMITMENT_STO_CH BadI for checking if commitments for STOs are active
    ME_COMMTMNT_PO_RELEV Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_PO_REL_C Check for Commitment-Relevance of Purchase Orders
    ME_COMMTMNT_REQ_RELE Check of Commitment Relevance of Purchase Requisitions
    ME_COMMTMNT_REQ_RE_C Check of Commitment Relevance of Purchase Requisitions
    ME_DEFINE_CALCTYPE Control of Pricing Type: Additional Fields
    ME_DP_CLEARING Clearing (Offsetting) of Down Payments and Payment Requests
    ME_FIELDSTATUS_STOCK FM Account Assignment Behavior for Stock PR/PO
    ME_GUI_PO_CUST Customer's Own Screens in Enjoy Purchase Order
    ME_HOLD_PO Hold Enjoy Purchase Orders: Activation/Deactivation
    ME_INFOREC_SEND Capture/Send Purchase Info Record Changes - Internal Use
    ME_PO_PRICING Enhancements to Price Determination: Internal
    ME_PO_PRICING_CUST Enhancements to Price Determination: Customer
    ME_PO_SC_SRV BAdI: Service Tab Page for Subcontracting
    ME_PROCESS_COMP Processing of Component Default Data at Time of GR: Customer
    ME_PROCESS_PO Enhancements for Processing Enjoy Purchase Order: Intern.
    ME_PROCESS_PO_CUST Enhancements for Processing Enjoy Purchase Order: Customer
    ME_PROCESS_REQ Enhancements for Processing Enjoy PReqs: Internal
    ME_PROCESS_REQ_CUST Enhancements for Processing Enjoy PReqs: Customer
    ME_PURCHDOC_POSTED Purchasing Document Posted
    ME_RELEASE_CREATE BAdI: Release Creation for Sched.Agrmts with Release Docu.
    ME_REQ_OI_EXT Commitment Update in the Case of External Requisitions
    ME_REQ_POSTED Purchase Requisition Posted
    ME_TAX_FROM_ADDRESS Tax jurisdiction code taken from address
    ME_TRF_RULE_CUST_OFF BADI for Deactivation of Field T161V-REVFE
    ME_TRIGGER_ATP Triggers New ATP for Changes in EKKO, EKPO, EKPV
    ME_WRF_STD_DNG PO Controlling Reminder: Extension to Standard Reminder
    MM_DELIVERY_ADDR_SAP Determination of Delivery Address
    MM_EDI_DESADV_IN Supplementation of Delivery Interface from Purchase Order
    SMOD_MRFLB001 Control Items for Contract Release Order
    AMPL0001  User subscreen for additional data on AMPL             
    LMEDR001  Enhancements to print program                          
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from 
    LMEQR001  User exit for source determination                     
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail       
    M06B0001  Role determination for purchase requisition release    
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number                       
    M06B0004  Number range and document number                       
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents 
    ME590001  Grouping of requsitions for PO split in ME59           
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N           
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number                       
    MM06E004  Control import data screens in purchase order          
    MM06E005  Customer fields in purchasing document                 
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator             
    MM06E010  Field selection for vendor address                     
    MMAL0001  ALE source list distribution: Outbound processing      
    MMAL0002  ALE source list distribution: Inbound processing       
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses                             
    MMFAB001  User exit for generation of release order              
    MRFLB001
    Regards,
    Anirban

  • 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

  • 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...

  • 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

  • HOT TO SET THE OUT PUT MESSAGE FOR PURCHASE ORDER

    As i was saving the Purchase order in Me21n the error message that came up was " NO OUTPUT MESSAGE SET FOR THE PO " HOW  DO I SET THE OUTPUT MESSAGE AND SET THE PO PRINT SETTING KINDLY HELP.

    Hi
    First of all Execute  program RSNAST0F in SA38 .
    Following are some steps for PO message printing
    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---> ZNEU
    Select “ZNEU” and double click on “Mail title and texts” and go to
    EN- New Purchase Order Print Out,
    Select “ZNEU” again and double click on “Processing routines,
    Select “ZNEU” 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
    ZNEU -> ZNB
    Now you create PO(ME21N) and maintain the text and save it. Go to ME22N and print the PO by giving output type ZNEU).
    Vishal...

  • I found a exit CIFPUR02 for purchase order inbound process.is it suitable?

    I found a exit CIFPUR02 for purchase order inbound process.is it suitable?
    my idoc is PORDCR102 AND message type is PORDCR1. my requirement is this is EXIT should trigger before saving the data in me21n.
    Edited by: rk.kolisetty on Jun 24, 2010 4:59 PM

    Hi,
    Following are the user exit relevant to T Code ME21n.
    AMPL0001  User subscreen for additional data on AMPL
    LMEDR001  Enhancements to print program
    LMEKO001  Extend communications structure KOMK for pricing
    LMEKO002  Extend communications structure KOMP for pricing
    LMELA002  Adopt batch no. from shipping notification when posting
    LMELA010  Inbound shipping notification: Transfer item data from
    LMEQR001  User exit for source determination
    LMEXF001  Conditions in Purchasing Documents Without Invoice Rece
    LWSUS001  Customer-Specific Source Determination in Retail
    M06B0001  Role determination for purchase requisition release
    M06B0002  Changes to comm. structure for purchase requisition rel
    M06B0003  Number range and document number
    M06B0004  Number range and document number
    M06B0005  Changes to comm. structure for overall release of requi
    M06E0004  Changes to communication structure for release purch. d
    M06E0005  Role determination for release of purchasing documents
    ME590001  Grouping of requsitions for PO split in ME59
    MEETA001  Define schedule line type (backlog, immed. req., previe
    MEFLD004  Determine earliest delivery date f. check w. GR (only P
    MELAB001  Gen. forecast delivery schedules: Transfer schedule imp
    MEQUERY1  Enhancement to Document Overview ME21N/ME51N
    MEVME001  WE default quantity calc. and over/ underdelivery toler
    MM06E001  User exits for EDI inbound and outbound purchasing docu
    MM06E003  Number range and document number
    MM06E004  Control import data screens in purchase order
    MM06E005  Customer fields in purchasing document
    MM06E007  Change document for requisitions upon conversion into P
    MM06E008  Monitoring of contr. target value in case of release or
    MM06E009  Relevant texts for "Texts exist" indicator
    MM06E010  Field selection for vendor address
    MM06E011  Activate PReq Block
    MMAL0001  ALE source list distribution: Outbound processing
    MMAL0002  ALE source list distribution: Inbound processing
    MMAL0003  ALE purcasing info record distribution: Outbound proces
    MMAL0004  ALE purchasing info record distribution: Inbound proces
    MMDA0001  Default delivery addresses
    MMFAB001  User exit for generation of release order
    MRFLB001
    Rgd,
    Chetan

Maybe you are looking for