Forms for Purchase order and Outline agreement

In my previous work which was in 4.7, smart tables and of course with the in-house development were used in order to activate country specific functionalities in P2P forms, such as PO, contracts, SA and RFQ printouts.
This functionalities are usually language, paper size and the content like specific country address, logos, tax display, etc.
So, the question is if the 6.0 version has any sort of localization or part of it for all or some countries that we can us as a base?

No such specific settings were introduced in ECC6.0.
Better proceed with customized Forms only
Umakanth

Similar Messages

Report for purchase requisition, purchase order and schedulling agreement.

Hi, thanks for your help.
I need a report or query just to view in one screen the related docs. as purchase requisition, purchase order and schedulling agreement.
I don´t know if there is a table or trx. with that information.
Is it possible to get that information via query ?
Thanks for your help.
Regards.

For PR and PO you can use ME5A
For PR and Scheduling agreements also you can use ME5A.

SMART FORM FOR PURCHASE ORDER

Hii Experts,
I am developing a smart form for purchase order. I am customizing the existing PO smart form according to the clients requirements. The customer needs fields Discount percentage, Excise duty and VAT/CST%... all these fields when i explored in transaction me23n come from a structure so the values come only at run time.. can anyone tell me the exact table and fields from where these comes so that i can retrieve it from there and display it in my smart form. The fields i need are discount percentage, excise duty and VAT/CST%. its urgent.

REPORT ZMR_PURCHASE_ORDER.
types: BEGIN OF ty_lfa1,
          LIFNR TYPE lfa1-LIFNR,
          MCOD1 TYPE lfa1-MCOD1,
          STRAS TYPE lfa1-STRAS,
          MCOD3 TYPE lfa1-mcod3,
      END OF ty_lfa1.
TYPES: BEGIN OF ty_ekpo,
          ebeln TYPE ekpo-ebeln,
          ebelp TYPE ekpo-ebelp,
          txz01 TYPE ekpo-txz01,
          menge TYPE ekpo-menge,
          peinh TYPE ekpo-peinh,
          brtwr TYPE ekpo-brtwr,
      END OF ty_ekpo.
TYPES: BEGIN OF ty_ekko,
        ebeln TYPE ekko-ebeln, "purchase doc
        LIFNR TYPE ekko-LIFNR, "vendor
        MCOD1 TYPE lfa1-MCOD1, "vendor name
        STRAS TYPE lfa1-STRAS, "vendor add
        MCOD3 TYPE lfa1-MCOD3, "vendor city
        bedat TYPE ekko-bedat, "doc date
        unsez TYPE ekko-unsez, "contact person
        verkf TYPE ekko-verkf, "attn
        telf1 TYPE ekko-telf1, "tele
        ihrez TYPE ekko-ihrez, "ref
        KNUMV TYPE ekko-KNUMV, "doc condition
       ebelp TYPE ekpo-ebelp, "item
       txz01 TYPE ekpo-txz01, "message desc
       menge TYPE ekpo-menge, "qty
       peinh TYPE ekpo-peinh, "rate
       brtwr TYPE ekpo-brtwr, "gross
    END OF ty_ekko.
TYPES: BEGIN OF ty_t685t,
        kschl TYPE t685t-KSCHL,
        vtext TYPE t685t-vtext,
      END OF ty_t685t.
TYPES: BEGIN OF ty_line_item,
        KNUMV TYPE konv-KNUMV, "condition number
        STUNR TYPE konv-STUNR, "step
        kposn TYPE konv-kposn, "item
        KSCHL TYPE konv-KSCHL, "condition type
        vtext TYPE t685t-vtext, "condition name
        KAWRT TYPE konv-KAWRT, "base amt
        KRECH TYPE konv-KSCHL, "calculation type
        qty(13) TYPE n,         "qty
        kbetr TYPE konv-kbetr, "condition rate
        kwert TYPE konv-kwert, "condition value
    END OF ty_line_item.
data: wa_ekko TYPE zms_ekko,
      wa_item TYPE zms_konv,
      wa_lfa1 TYPE ty_lfa1,
      wa_t685t TYPE ty_t685t,
      wa_ekpo TYPE ty_ekpo.
data: it_ekko TYPE TABLE OF zms_ekko,
      it_item TYPE TABLE OF zms_konv,
      it_lfa1 type TABLE OF ty_lfa1,
      it_t685t TYPE TABLE OF ty_t685t,
      it_ekpo TYPE TABLE OF ty_ekpo.
SELECTION-SCREEN : BEGIN OF BLOCK ss_block WITH FRAME TITLE text-001.
   PARAMETERS: pa_ver(2) TYPE c DEFAULT '0'.
    SELECT-OPTIONS: pa_pord FOR wa_ekko-ebeln,
                    pa_date for wa_ekko-bedat.
SELECTION-SCREEN : END OF BLOCK ss_block.
SELECT EBELN LIFNR bedat unsez verkf telf1 ihrez knumv from ekko
    into CORRESPONDING FIELDS OF TABLE it_ekko.
if pa_pord is not INITIAL.
    DELETE it_ekko WHERE ebeln not in pa_pord.
endif.
if pa_date is not INITIAL.
    DELETE it_ekko WHERE bedat not IN pa_date.
endif.
if it_ekko is not INITIAL.
SELECT lifnr MCOD1 STRAS MCOD3 from lfa1
    INTO CORRESPONDING FIELDS OF TABLE it_lfa1
    FOR ALL ENTRIES IN it_ekko
    WHERE LIFNR = it_ekko-LIFNR.
SELECT ebeln ebelp txz01 menge peinh brtwr from ekpo
    INTO CORRESPONDING FIELDS OF TABLE it_ekpo
    FOR ALL ENTRIES IN it_ekko
    WHERE EBELN = it_ekko-ebeln.
loop at it_ekko into wa_ekko.
    READ TABLE it_lfa1 into wa_lfa1 WITH KEY lifnr = wa_ekko-LIFNR.
    wa_ekko-MCOD1 = wa_lfa1-MCOD1.
    wa_ekko-stras = wa_lfa1-stras.
    wa_ekko-MCOD3 = wa_lfa1-MCOD3.
    MODIFY it_ekko FROM wa_ekko TRANSPORTING MCOD1 STRAS MCOD3 WHERE ebeln = wa_ekko-ebeln.
ENDLOOP.
SELECT KNUMV STUNR KPOSN KSCHL KRECH kbetr kwert KAWRT from konv
    into CORRESPONDING FIELDS OF TABLE it_item
    FOR ALL ENTRIES IN it_ekko
    WHERE KNUMV = it_ekko-KNUMV.
SELECT kschl vtext from t685t
    INTO CORRESPONDING FIELDS OF TABLE it_t685t
    FOR ALL ENTRIES IN it_item
    WHERE spras = 'EN' and KSCHL = it_item-KSCHL.
LOOP AT it_item into wa_item.
    READ TABLE it_t685t into wa_t685t with key KSCHL = wa_item-KSCHL.
    wa_item-vtext = wa_t685t-vtext.
    if wa_item-kschl = 'ZBP1'.
      wa_item-qty = wa_item-KAWRT / wa_item-kbetr.
    endif.
    if wa_item-KRECH = 'A'.
     wa_item-kbetr = wa_item-kbetr / 10.
    endif.
    if wa_item-kschl = 'NAVS'.
      wa_item-vtext = 'Sales Tax'.
    endif.
    MODIFY it_item from wa_item TRANSPORTING vtext kbetr kschl qty
      WHERE stunr = wa_item-STUNR and
            kposn = wa_item-kposn.
ENDLOOP.
DELETE it_item WHERE kposn = '000000'.
DELETE it_item WHERE kschl <> 'ZBP1' and kschl <> 'ZD01' and kschl <> 'ZE01'
      and kschl <> 'NAVS' and kschl <> 'ZSRV'.
sort it_item by kposn STUNR.
CALL FUNCTION '/1BCDWB/SF00000025'
EXPORTING
    ARCHIVE_INDEX              =
    ARCHIVE_INDEX_TAB          =
    ARCHIVE_PARAMETERS         =
    CONTROL_PARAMETERS         =
    MAIL_APPL_OBJ              =
    MAIL_RECIPIENT             =
    MAIL_SENDER                =
    OUTPUT_OPTIONS             =
    USER_SETTINGS              = 'X'
IMPORTING
    DOCUMENT_OUTPUT_INFO       =
    JOB_OUTPUT_INFO            =
    JOB_OUTPUT_OPTIONS         =
    TABLES
      it_ekko                    = it_ekko
      it_item                    = it_item
EXCEPTIONS
    FORMATTING_ERROR           = 1
    INTERNAL_ERROR             = 2
    SEND_ERROR                 = 3
    USER_CANCELED              = 4
    OTHERS                     = 5
IF sy-subrc <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
        WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ENDIF.
endif.

What is Tcode for purchase order and purchse requisition.

HI all
What is Tcode for purchase order and purchse requisition.
Thanks

Hi Melanie,
How are you trying to check for the PR number? Are you accessing it via Portal (IE) or the GUI?
If you are trying to get the PR number for a SC through Portal. Then please follow the below process.
Go to the SC > Related Documents tab
The related Documents tab should have all the follow-on document number along with the type of document.
If you are trying to get the PR number for a SC through GUI, then:
Go to transaction BBP_PD in GUI > Give the Object Types as BUS2121 and the Object ID as the SC number and click on F8.
Once you have opened the SC then scroll down till you get the Header Links and click on the line.
This should display the document that is linked to the SC.
Hope this helps.
Regards

Difference between Purchase Order and Scheduling Agreement

Can any one explain the main differences between a Purchase Order and a Scheduling Agreement?
Thanks in advance

Hi,
A Purchase Order is a document that is given to Vendor to indicate our intention to buy goods from them. It contains what is the desired goods, how much quantity, price, and the delivery date, among other things.
A standard procurement cycle for this is:
PR --> PO --> GR --> IV
A Scheduling Agreement however, is a type of an Outline Agreement. Outline Agreements are divided into 2, first one is Contracts and second is Scheduling Agreement. So this is basically a long term agreement with a particular vendor that contains details on what is the desired goods, quantity, and the exact delivery dates.
A standard cycle for this is:
PR --> Create Scheduling Agreement --> Maintain Delivery Schedule (agreed dates on when vendor will send the goods and time) --> GR --> IV
As you can see, for Scheduling Agreement, PO is not required, but instead we would need to Maintain Delivery Schedule.
Just to share on Contracts, it appears as below:
PR --> Contract Creation --> PO --> GR --> IV
Regards,
Nazrin

How to set print form for Purchase order in SPRO txn.

Hi,
I need to find out the name of the smartform used to print purchase order.
Cheers
Senthil

HI,
go to SPRO - MM - Purchasing - Messages - Output Control - Message Types - Define Message Types for Purchase Order
select the message tyoe and then click on processing routines and you will get the form name..
Thanks & Regards,
Kiran

Report for Purchase orders and deliveries

Hi all,
Is there any report in SAP that gives me the list of purchase orders and the deliveries associated with those PO's.
Please advise.
Thanks in advance
Sruthi

Hi,
What kind of delivery are you looking for ??
If it's inbound delivery, use VL06I tcode & for outbound, try VL06O
Thanks & Best Regards,
Devendra Gaware
PS - Reward if found useful.

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

GR for Purchase order and GI for prod. order simultaneously

Hi Guys,
My client current has an external system, which does both GR for puchase order and GI for Prod. order at the same time. He is now migrating into SAP and he wants the same functionality. Do you have any idea how to do this.
For eg., Pick list(CO27) will pick and issue the components to production order, if the component is in inventory. if it is not there, it will give error.
Can we add, if material is not there, it should do GR and GI. is it possible with any customer exit in CO27?
Thanks
Srini

Hi,
In KANBAN, we have the possibility to do the GR (Goods Invard) if th container is Full and GI (to the production Order) if the Container is Empty.
It's just a thaught..
Regards,
Siva

Attachment for Purchase Order and Purchasing Requisition

Dear All,
At the moment we are on ECC6 EHP 4 and would like to use Document Management in SAP. Now att the PO and PR line item we need to click the Documents icon to see the if the is any document that is being attached to the line item . Is there any way that we can have and indicator at the PR or PO item to denote that there is an attachment attach without the need to click the Documents icon? Maybe an attachment symbol that outlook use whenever there is an attachment in the email.
Would appreciate if you provide any notes or configuration step how to do this.
Thanks

A purchase requisition is an internal document that's created to initiate a procurement transaction. The requisition is created to identify the materials that are needed to be acquired and when they're needed. Once completed by the initiator, it's sent to the appropriate approvers.
Upon approvals of the requsition have been provided, and a vendor is selected, a purchase order is created. The purchase order is an external document whereby an agreement is made to procure the materials at an agreed upon price and delivery schedule
The InfoCubes for each of these is different due to the nature of the documents (internal v. external).

Look for 'Purchase Order' and 'Due date' Tables

Hi Everyone,
iam creating a Form for an automatic payment and i have some difficulties to find the table of these fields :
- Purchase Order (EBELN)
- Due date (NETDT)
Please can u help me?
Regards.

I hope you checked these tables.
I found these on Where-used for your NETDT field, Alos these tables have field BELNR which might intrests you.
Table Fields                     Short descriptn
BWPOS                            Valuations for Open Items
FAEDT                            Due Date for Net Payment
DKKOP                            Balance Audit Trail
NETDT                            Due Date for Net Payment
DKOKP                            Open Item Account Balance Audit Trail
NETDT                            Due Date for Net Payment
DSKOP                            Balance Audit Trail
NETDT                            Due Date for Net Payment
MHND                             Dunning Data
FAEDT                            Due Date for Net Payment
good luck,
ags.

Table for Purchase Order and Non Purchase order history

Hi,
Could you please share me the table name for getting the Purchase order history and Non purchase order history because this is a client requirent.
I have gone through this tables but not getting exact data i.e. EKPO,EKKO,EKNE...
please share with me the exact Table name to get all the Purchase order history and not purchase order history..
Thanks in advance

Hi Mallikarjun,
Where did you find the non po info?
Thanks,
Neha

Modification in MEDRUCK for purchase order, RFQ, scheduling agreement.....

Hi all
I have requirment in which i have to modify standard script MEDRUCK for PO, RFQ, SCHEDULING AGREEMENT, AND QUANTITY CHART.
I know how to modify standard layouts but after modifying layouts what to do next??
How can i use same medruck script for RFQ, SCHEDULING AGREE, AND QUANTITY CONTRACT.
help me out!!!!!!!!!!

hai manisha,
Actually SAP Clubbed all the requriments And Made one FORM for one bussiness scenario.
So Depending On The Transaction That We Are Running System Will Automatically Triggers Particular Type.
So Take A Copy Of Medruck For Each Document That U have To Do.
Then Run Respective Transactions Then According to that configure NACE.
In NACE transaction, We will assign the Form name and the driver program name and the corresponding routine to be triggered in the driver program.
We should be able to tell the system to pick up the desired form layout and trigger the routine and get the data from the database and put it on to the form. All these stuff the system will come to know from the NACE settings.
NACE is used to create output type while creating the output type you will mention forms, and driver program.
that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
so check in NAST, TNAPR table
You can view all forms and driver programs for standard SAP Scripts.
Assigning Form and Driver proram to an Output type is as follows.
1) Go to NACE transaction
2) Select an Applicatin(V1-Sales,V2-Shipping,V3-Billing)
3) Click on Outputtypes Button
4) Comes to Change Mode
5) Click on New Entries button
6) Specify Output type,Form name and Program and Save it.
Check these links
/people/venkata.ramisetti/blog/2006/09/21/configuring-output-types-for-pdf-based-print-forms
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1989fe43b111d1896f0000e8322d00/frameset.htm
Condition records in NACE?
IF Found Helpfull Do Reward.
Regards.
Eshwar.

Lead time for Purchase Orders and Goods R. (EKBE-EKET)

Hi all,
has anyone already implemented a logic for calculating
the lead time between delivery date (EKET-EINDT) and the
goods receipt date (EKBE-BUDAT) for extraction to BW?
I have the problem, that i have more than one schedule line. There you cant link the GR (EKBE) to the relevant schedule line (EKET). How can i implement the FIFO solution (FirstinFirstout)?
Example:
EKET
DocNr_Pos__ETENR__Quantity____EINDT
6700___10__1_______100________20060601
6700___10__2_______300________20060701
EKBE
DocNr_Pos__Nr__Quantity__Budat
6700___10__1_____200_____20060603
6700___10__2_____200_____20060702
Result should be:
DocNr_Pos_ETENR__Quantity__Deliverydate__ZBUDAT(from ekbe)
6700___10__1_______100________20060601___20060603
6700___10__2_______300________20060701___20060702
20060702 therefor because the the full quantity arrived at
this date.
Thank you very much for your help or any codings, best regards
Frank

HI Horny,
Can you use the Following Tables:
S039 - > LETZTABG - Date: last (i.e. most recent) goods issue
EKPO -> EBELN - Purchasing Document Number.
You can create View by using these two tables (Material Number is the Common) and uploade the data.
Hope this will be helpful for your question.
Thanks
Rajesh
Message was edited by:
rajesh

What is Sap Scripts for purchase order

hai,
what is the sap script or smart form for purchase order,
and how to modify the existing standerd one.
explain me in step by step.

hi
Please ask question on sapscript in sapscript forum.
use sap script form medruck for PO
SmartForm /BPR3PF/MMPO_L is the standard delivered Purchase Order in 4.6c
Transaction code m/34 allows you to associate your 'Y' copy of the standad PO to your included company specific PO requirements such as company log graphic and other particulars.
Go to transaction OMFE. Tell me what you see there for the output type you are interested in. Let me take the standard output type NEU. The entry looks something like this.
NEU Purchase order 1 SAPFM06P ENTRY_NEU MEDRUCK.
The first one is your output type, next is its description, next is the medium, then the program, routine, and the form name.
You already copied the layout MEDRUCK to ZMEDRUCK. Now copy SAPFM06P to ZZSAPFM06P. Now ENTRY_NEU routine is in the include FM06PE02. You need to make your changes here to accommodate for the new field. So copy this include to ZZFM06PE02 and make your changes. Also, in ZZSAPFM06P, change the line where it says INCLUDE FM06PE02 to INCLUDE ZZFM06PE02.
Now in this routine ENTRY_NEU, there is a function module call ME_READ_PO_FOR_PRINTING which reads in the PO data from the tables. We need to copy this function module as well as this is where you will do your extra selections for the new fields. You will do the same with the other function call ME_PRINT_PO, if you need to change anything on the print.
after this to define output type...
NACE
You can track the form and the print program used for that form
NACE is used to create output type while creating the output type you will mention forms, and driver program.
that will be maintained in the table TNAPR.if you create the output type using NACE then it will be automatically visible in table NAST and TNAPR.
so check in NAST, TNAPR table
http://help.sap.com/saphelp_erp2005/helpdata/en/c8/1989fe43b111d1896f0000e8322d00/frameset.htm
Condition records in NACE?
EX--in simple terms..take a transaction say ME21N ( Purchase Order ), u can see a Print icon there. now when u click on this icon, it has to print the PO document. Now how does it do that? when u click Print, the control gets transffered to a print program, now which program gets triggered is decided by what program name u specify in NACE.
So in NACE>EF>Output Type>NEU>processing routine--> u can see some standard program already configured( maybe SAPFM06P n form MEDRUCK )..these are the programs n sapscript that gets executed wen u say "PRINT" in the transactrion...so u can customise the print program for customer changes over here by copying the standard program n form into a Z/Y one and replacing the program names in NACE.
Yogesh N
Edited by: Yogesh N on Aug 20, 2008 3:19 AM

Forms for Purchase order and Outline agreement

Similar Messages

Maybe you are looking for