HELP regarding reconiciliation of Purchase orders system

What the need is:
A report per country that shows PO no., amount of PO, Goods recived amount and total invoiced amount by a date, because the total amount of the GR amount for the country has to be identical with the open amount on the GL account. And it is at company code level.
~Regards
Edited by: aakansha kumar on Sep 28, 2009 12:18 PM

There is no report "per country" , you can get most of your information from ME2M ( but not directly , ull need to take dump in excel and use formulas :P ) .
Other reports which may be helpful are ME80FN , MB5S .

Similar Messages

Please send me fm regarding to get purchase order and change purchase order

Hi,
Please send me fm regarding to get purchase order and change purchase order .
Regards,
Gurprit Bhatia

Hi,
Function module to get the purchase order details:
BAPI_PO_GETDETAIL.
data: po_items type table of bapiekpo with header line.
parameters: p_ebeln type ekko-ebeln.
call function 'BAPI_PO_GETDETAIL'
exporting
    purchaseorder                    = p_ebeln
ITEMS                            = 'X'
ACCOUNT_ASSIGNMENT               = ' '
SCHEDULES                        = ' '
HISTORY                          = ' '
ITEM_TEXTS                       = ' '
HEADER_TEXTS                     = ' '
SERVICES                         = ' '
CONFIRMATIONS                    = ' '
SERVICE_TEXTS                    = ' '
EXTENSIONS                       = ' '
IMPORTING
PO_HEADER                        =
PO_ADDRESS                       =
tables
PO_HEADER_TEXTS                  =
   po_items                         = po_items
PO_ITEM_ACCOUNT_ASSIGNMENT       =
PO_ITEM_SCHEDULES                =
PO_ITEM_CONFIRMATIONS            =
PO_ITEM_TEXTS                    =
PO_ITEM_HISTORY                  =
PO_ITEM_HISTORY_TOTALS           =
PO_ITEM_LIMITS                   =
PO_ITEM_CONTRACT_LIMITS          =
PO_ITEM_SERVICES                 =
PO_ITEM_SRV_ACCASS_VALUES        =
RETURN                           =
PO_SERVICES_TEXTS                =
EXTENSIONOUT                     =
check sy-subrc = 0.
loop at po_items.
write:/ po_items.
endloop.
Check this program too:
RFFMFG_INV_CANC_ALL for BAPi_PO_GET_DETAIL.
Hope it helps you.
Regards,
Anjali

Regarding building a purchase order smart form

hi guys,
i got to design a purchase order smart form which consists of 3 pages and i need to enclose " terms and conditions " on the back side of every page. To be more elaborative on first page purchase order details and back side of it " terms and conditions " and same way on other 2 pages.
how do i do it, can any one help me with this.
thank you very much
pavan

Hi
If the smartform purchase order is not available in your system
means you can download the form IDES and you can upload the form in ur ecc 6.0 system.we faced a similar kind of problem in our system and we did as i said.
Once you uploaded the things you can easily view the form interface and rest of the things related to smartforms.
Thanks and Regards
Arun Joseph

Regarding material wise purchase order creation with reference to pr

Dear sir
I have a scenario depending on the material wise pos creation
I have two type of material
1) raw material
2) consumables
When user will create purchase order for raw material, system should ask purchase requisition. ( i.e with out purchase requisition for raw material , system should not allow to create the purchase order)
Where as for all consumables materials system should allow to create the purchase order
Without purchase requisition also, for user.
Regards
Jrp.

You have to create two different document type for purchase order.
1) Raw Material Purchase
2) Consumables Purchase
You can create two different document type for purchase order with below mention path: -
SPRO >> Materials Management >> Purchasing >> Purchase Order >> Define Document Types.
After define two different document type, You can change field status for two different document type with below mention path.
SPRO >> Materials Management >> Purchasing >> Purchase Order >> Define Screen Layout at Document Level.
Select document type and change field status of purchase requisition.
Regards,
Mahesh Wagh

Regarding Report on purchase order purchase requesition and GRN No.

Dear All,
              I am creating ALV report in which. I want all purchase order (EBELN), their respetive Purchase Requesition(BANFN)
              And GRN No(MBLNR)., if they are created. But all purchase order should be displayed evenif their GRN have not been
             made. GRN only haveing movement type 101 and 102. i.e. of 50 series and not 49 series.
                              i want tlike this
For Ex:-
                      EBELN           BANFN          MBLNR
                  45000223       1000223       5000080
                  45000245                            5000056
                 45000676
                 45000848     .

Hi,
1. Fetch all the Purchase Orders from EKKO
2. Fetch Purchase Req from EBAN for all entries in above selected internal table where EBELN = EKKO-EBELN
3. Fetch GR info from EKBE for all entries in first selected internal table where EBELN = EKKO-EBELN and VGABE = '1'. (this indicates GR for a PO) and BWART in ('101', '102').
4.
Loop through EKKO.
        T_FINAL-EBELN = EKKO-EBELN.
        Read EBAN with key EBELN = EKKO-EBELN.
        T_FINAL-BANFN = EBAN-BANFN.
        Loop through EKBE where EBELN = EKKO-EBELN. (there can be multiple docs for a single PO)
             T_FINAL-MBLNR = EKBE-MBLNR.
             Append T_FINAL.
        Endloop.
        If SY-SUBRC is not equal to 0. (If no GR happend, control will not go to EKBE loop, still you need to display it in ALV)
            Append T_FINAL.
       Endif.
    Endloop.
5. Display the contents of T_FINAL in ALV.
Hope this helps you !!!
Regards,
Ganga

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

Help Regarding Xi integrating with Seibel System.

HI @,
I have to intergrate a seible system with R/3 but I haven't worked on the same before.
I need help regarding seibel inetrgartion scenarions and various adapters that can be used in that conditions.
Documents on Seible Integration will b really helpful.
Regards

It would be better to go for the iway adapter for this integration requirement. The other documents can be obtained direclty from iway
Regards,
Prateek

Contracts and Purchase Order system messages

Hi All,
I have a couple of questions relating to system messages that are related to purchase orders created with reference to contracts.
1. When should message 06 155 called? If I create a purchase order with reference to a Value Contract (WK) where the total purchase order value is equal to the Contract Target Value I would expect the message to be called as either a warning or error depending on the system settings (it is currently set as a warning). However in my system the message is not generated.
I can get the message to generate if I put the PO on hold, then change the value of the PO above the contract target value and then set it back to equal the contract target value but this hardly seems the correct way the message should be called.
2. Is there a standard way to restrict which purchase order document types can be created with reference to a contract?
Cheers
Chris

Hi Jurgen,
thanks for the response. I know that the message should be called if the total PO value is equal to the Target Value of the contract, however in my system this doesn't happen.
Example
Contract has Target Value of £1,000,000 (Target Qty is 0 and Price is £1)
Field ktwrt = £1,000,000
PO created with qty 1,000,000 and price £1 (i.e. value = £1,000,000) but the message is not generated. If I change the qty to be 1,000,001 then message 06 042 is correctly generated.
Is the message 06 155 generated correctly in your system? or I am missing someconditions that don't match between my PO and contract?
Cheers
Chris

Need help regarding mm best purchasing practices..

hi
could any one tell me about the sap mm best purchasing practices.

Here find below for the best practices that can be considered in General
1) Master Data
a) Central Master data with uniform naming convention
b) Master Maintenance tool (MDM) with workflow for approval
2) Collection of Requirements from User departments and Approval-
a) Creation of PR in SAP and Release strategy with work flow
b) PR creators and PR Release authorities (work flow) are linked with HR org structure.
c) Approval/Notifications for in action/Reminders can be routed with the help of workflow.
3) Budget Control for PR-
a) By activating Funds Management OR
b) By Internal Order OR
c) Customer Exit to validate The PR value/Price according to allocated budget
4) Buyer activity
a) Automatic source determination and automatic creation of PO with release strategy.
b) PO creation with reference to Long term contract (Release orders) for regular vendors plus Global contract
c) Uniform way of raising PO with terms and conditions
c) RFQ for Bidding Process plus release strategy.
d) Vendor rating
e) PO Price Difference Tolerance check/Validation in comparison with PR.
5) GRN
a) Central warehouse
b) Acceptance of Materials subject to quality check
c) Normal Service Procurement with Service Master
d) Service entry sheet with release strategy.
5) Invoice
a) Invoice Block parameters/Tolerances
b) Invoice Approval work flow
c) GR based invoice Verification for Normal Purchase.
d) Activate Material Ledger to overcome the disadvantages of posting Invoice with Price difference in terms of valuation
e) Uniform way of Invoice Posting/Payment
f) ERS

** Urgent help *** Reg : Confirmations in Purchase orders .

Hi all ,
I have one requirement where the report should display open PO.s
with the materials which are 'AB' confirmed but not ' CO' confirmed before the delivery date .
I developed the report with these conditions .
My question is ' Is there any field in the table ekes or any table
stating that this particular material would be having ' CO' Confirmations
for the AB confirmed date '
Regards,
Amarnath Reddy.

Dear Amarnath
The Confirmation category like AB,etc is define in config per Confirmation Control Key, so you should check to EKPO-EKPO for the conf.control key , and check to table T163G for the confirmation cat ,then you compare it to EKES with reference PO number and item.So i think you can consider this logic for your report development.
Regards,
w1n

ME80FN evaluation regarding Purchase Order History (Execute in BackGround)

Hi,
I need your help regarding the follwowing Situation: I want to make an avaluation regarding the Purchase Order History for a few thousend of purchase orders in ME80FN. Becasue of the big amount of purchase orders I have to execute the program in Background. After executing the program in background in the created spool I get the Information regarding the Header of the purchase orders NOT REGARDING THE PURCHASE OREDR HISTORY.
Is there any way to start a background programm with some kind of a parameter so it can deliver the Purchase Order History information i need. Another way to solve the problem would be to set up a default value for the ME80FN transaction so the default delivered Information would be regarded to the Purchase Order History not to the Header Information?
Regards & Thanks for your help
Bogdan

I know this does not anser yoru question but, The last time I ran it I could comfortably do it for a long time .. Foreground.. WOuld you have issues running it in teh foreground.. May be BASIS could help tuning the run time

Outbound Purchase order user exit EXIT_SAPLEINM_002 help

Hi,
Can somebody tell me how to stop the IDOC processing if the conditions are not met? My detail question is
I am modifying the data in the outbound IDOC (IDOC_OUTPUT_ORDERS) for purchase order. I am using the user exit EXIT_SAPLEINM_002 to modify the segment data.
But I would like to know how to stop for creating the IDOC if one of the condition will not met (for example if there is no data in Ztable while fetching then IDOC should not be created )?
If the condition will fail I don't want to create the IDOC but Purchase order has to create in R/3.
Any suggestions on my above query is highly appreciable.
Regards,
Noorul

Hi
The purchase order should always be created because it's created before creating the IDOC, I suppose it will be created by a particular message.
Have you tried to raise the exception DATA_NOT_RELEVANT_FOR_SENDING?
Max

Purchase order to payment cycle report

Dear Sir/Madam
We want to have a report on the purchase order to payment cycle.
this includes the following points:
1. Purchase Requisition is raised in the system
2. PO is raised with various line items
3. Advance payment is done against the PO
4. GRN is made for goods delivered
5. Invoice is processed against each GRN
6. Retention is deducted to be paid in future
7. Liquidated damages (LD) is deducted which is treated as miscellaneous income in companys books
8. Payment is made to the vendor
We require the report in such a way which will give the details of each payment against each GRN line item. tracking of the same should be possible.
Do we have any standard report which will help in identifying the purchase order to payment cycle.
Thanks and Regards
Prashant P. Zinge

Hi,
It is always a requiremnet to have a report from PO, GR, IV to payment.
But unfortunately, SAP do not have such a report, we develop one locally, the difficult is at payment side.
Several invoices for one vendor has only one payment doc, how to display it need to discuss with end user.

Purchase order advance payment

Hi Friends,
Below is five requirement from my client regarding down payment and down payment request.
A) While posting down payment or down payment request Purchase order should require entry.
B) System should allowed to put purchase order for the same vendor against we posting advance payment or raising payment request.
C) If 100% advance has already paid against any purchase order, system should not allow to post any further advance against that purchase order.
D) If the 100% GRN has been done against any purchase order system should not allow to post any further advance against that purchaser order.
E) While paying advance system should consider the GRN or advance payment done against the purchase order, and system should allow the pay advance or raise the advance request less the value of advance or GRN value already done.
Your valuable input is highly appreciated.
Regards,
Ashu

Hi,
whatever Mr.Ajay has told correct 1 & 2
The 1 and 2 are possible using field status groups. You can make the PO mandatory
The rest are not possible in standard system.
but system will propose while posting down payment r down payment request amount more than PO value warning message has accrued but it will never stop for posting ok
one more solution is with the help of ABAPer we can able to stop - Use Substitution,
Mr. Ajay below mentioned Option for EHP4 is also available for in this ME2DP also never stop - more than PO value down payment r down payment request
Its a matter of discipline... however, explore the new feature of PO advance payment in EHP4, Tcode ME2DP. May be you get few answers there
Mahesh

In creation of purchase order

Dear All,
When ever I am creating a purchase order system issuing a warning messages like mentioned below:
Effective price lower than material price (variance > 30.00 %)
Effective price is 0.00 INR, material price is 80.00 INR
Can you suggest any body where we I am missing the customization.
Best Regards,
Krishna

Hi Krishna
U can set these tolerance in
SPRO>Materials Management->Purchasing>Purchase Order-->Set Tolerance Limits for Price Variance
Also check help provided by SAP for this
Set Tolerance Limits for Price Variance
In this step, you define the tolerance limits for price variances.
When processing a purchase order, the system checks whether the effective price of a PO item shows variances compared with the valuation price stored in the material master record. In addition, it checks whether the specified cash discount value is admissible.
Variances are allowed within the framework of tolerance limits. If a variance exceeds a tolerance limit, the system issues a warning or error message.
In the SAP System, the types of variance are represented by the tolerance keys. For each tolerance key, you can define percentage and value-dependent upper and lower limits per company code.
Standard settings
The standard SAP System supplied contains the following tolerance keys:
PE Price variance, Purchasing
Tolerance limit for system message no. 207. This message appears if the specified effective price exceeds the predefined tolerances when compared with the material price.
SE Maximum cash discount deduction, Purchasing
Tolerance limit for system message no. 231. This is a warning message, which appears when the specified cash discount percentage exceeds the predefined tolerances.
If u don't want this message to appear click Do not check tab by going above said SPRo path
Revert for any clarification
Vishal...

HELP regarding reconiciliation of Purchase orders system

Similar Messages

Maybe you are looking for