Subcontracting PO - GR/IR difference

Hi Masters,
When users do a GR to a subcontracting PO for the price maintained, an additional FI document with small price is created which is actually equal to the price of the posting resulted through movement '543' (price of subcontracting material). But, the finance team is asking to include that price also in the GR price, as it is annoying them to clear small (many) values every month.
Is there any way we can made settings in the system to do so. If my question is not clear, let me know, I will try to explain. Thanks!

This small posting is the amount you have pay the vendor! This amount (service cost) should go into GR/IR Clearing while the higher amount which is the material cost plus service cost of received material will be booked into Inventory.
This is perfect/standard value flow. And this posing has to be cleared by MIRO.

Similar Messages

What is the difference between Subcontracting PO and External refurbishment

What is the difference between Subcontracting PO and External refurbishment? How it affects valuation and material movements? When to be used which process?

Hi,
Check this link,
It would be useful for you.
http://searchsap.techtarget.com/search/1,293876,sid21,00.html?filter=on&query=difference%20between%20Subcontracting%20PO%20and%20External%20refurbishment&ctype=WEB&bucket=WEB&num=10&anum=&within=text
Reward for useful answers.

Difference between consignment and subcontract

hi,
Could anybody tell me what is the difference between consignment and subcontract?
Thanks a lot!

Dear Lauliu,
Under Consignment - there are vendor consignment and customer consignment categories.
Vendor consignment:In consignment processing, the vendor provides materials and stores them on your premises. The vendor remains the legal owner of the material until you withdraw materials from the consignment stores. Only then does the vendor require payment. The invoice is due at set periods of time, for example, monthly. In addition, you can also arrange with the vendor that you take over ownership of the remaining consignment material after a certain period of time.
http://help.sap.com/erp2005_ehp_05/helpdata/EN/4d/2b8f4c43ad11d189410000e829fbbd/frameset.htm
http://help.sap.com/erp2005_ehp_05/helpdata/EN/c6/af3c415e5dde2be10000000a1550b0/frameset.htm
Customer Consignment: http://help.sap.com/bestpractices/BBLibrary/HTML/J58_CustConsProc_EN_KO.htm
Sub-contracting: this can be operation sub-contracting/External Processing and product sub-contracting.
Regards
Mangalraj.S

Difference between Prod.PPM & a Subcontracting PPM

Guys,
I am working on the following subcontracti ng Scenario:
1. First Point to be noted "WE NOT PLANNING FOR THE COMPONENTS" . PLANNING IS DONE ONLY FOR THE FINISHED GOOD (FGI).
2. Plant will only have Componay owned Components stock (i.e for instance if an FGI reuires components 1,2 & 3 then our Company Plant will maintain stock only for 1. Therefore when a demand of 100 units of FGI comes from a DC to a plant. Based on the PPM (which has BOM in it) the plant will supply the required Quantity of component (1) Stock to the Vendor & the Vendor will mange by itself the number of components 2 & 3 & finally supply's the FGI to the Plant.
In this Scenario what kind of PPM do we have to send accross to APO plant?
Is it a Prod PPM or a Subcontracting PPM?? (This option of Prod PPM & Subcon PPM is present in the Integration model.)
Please advice.
Best regards,
KING

Hi ,
The main difference between normal and subcontracting PPM is that the subcontracting ppm is created at the vendor location in APO and creates planned order at the vendor location for generation of the dependent demand for components. In your case you only need to have component 1 in the BOM and the stock transfer to stock at subcontracting vendor for component 1 only.
As you said you can map it through the Subcontracting PPM with Vendor location in APO. There is also an alternate method in PPDS where you can create as a normal PPM without vendor location. you can refer to subcontracting in PPDS without source SAP help under crosslocation topics. But this has a constraint that if the same vendor is used by multiple plants then it is not recommended.
I would suggest you can map it through the subcontracting PPM in PPDS.
Let me know if it helps
Regards
Gaurav

Cost price differences in subcontracting PO's invoicing

Hello,
Which transaction key (of automatic postings) will be used by the system if I create an invoice for a subcontacting PO for a bigger value (in price) than the receipted?
Is it allways the PRD (Cost (Price) differences)? If not, on what does it depend?
Thanks!

Hello,
Thanks for all your replies (even if they were not 100% helpfull).
My problem is exactly the following:
For subcontrating PO's we have a price condition which imputates a % of the total cost to an account which will be payed to the carrier (this works perfectly) for the freight.
The problem is that if we try to invoice this document (which is not against the vendor of the PO but against a vendor which is the carrier) for more value than the expected then the Price Difference is not charged against any account! (the warning of the price tollerance is showed but the system doesn't know were to charge this difference).
Please help!
Thanks!!

REPORT FOR SUBCONTRACTING

DEAR FRIENDS,
I am making a program for tracking the materials given (mb1b 541 movt.) for subcontracting and taken by me (101 for actual good receipt, 543 for the given material- stock type inward, 545 for the scrap returns). but while i made the program i am unable to pick up the materials BOM from the PO which is essential to take the difference between these and the supplied quantities taken-in by GR.
following is the program.
Please suggest the changes. Thanks,
Deepak
*& Report ZMM_SUBCONTRACTING_PO_REPORT
*& Author:
*& Date :
*& Reason: Sub Contracting PO Report.
*& Find Discreprancy in PO and BOM. according to 543 and 545
REPORT ZMM_SUBCONTRACTING_PO_REPORT NO STANDARD PAGE HEADING
 LINE-SIZE 157.
*& TABLES DECLARATION
TABLES: EKKO,
 EKPO,
 EKBE,
 ENT5303.
*& SELECTION-SCREEN.
SELECTION-SCREEN: BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-001.
SELECT-OPTIONS: S_MATNR FOR EKPO-MATNR,
 S_WERKS FOR EKBE-WERKS OBLIGATORY.
PARAMETERS: P_BUKRS LIKE EKKO-BUKRS OBLIGATORY.
SELECT-OPTIONS: S_BUDAT FOR EKBE-BUDAT OBLIGATORY,
 S_EBELN FOR EKKO-EBELN,
 S_BELNR FOR EKBE-BELNR,
 S_GJAHR FOR EKBE-GJAHR.
SELECTION-SCREEN: END OF BLOCK B1.
*& INTERNAL TABLES DECLARATION.
DATA: BEGIN OF IT_EKKO OCCURS 0,
 EBELN LIKE EKKO-EBELN,
 END OF IT_EKKO.
DATA: BEGIN OF IT_EKBE OCCURS 0,
 EBELN LIKE EKBE-EBELN,
 EBELP LIKE EKBE-EBELP,
 GJAHR LIKE EKBE-GJAHR,
 BELNR LIKE EKBE-BELNR,
 BUZEI LIKE EKBE-BUZEI,
 BEWTP LIKE EKBE-BEWTP,
 BWART LIKE EKBE-BWART,
 BUDAT LIKE EKBE-BUDAT,
 MENGE LIKE EKBE-MENGE,
 DMBTR LIKE EKBE-DMBTR,
 LFBNR LIKE EKBE-LFBNR,
 MATNR LIKE EKBE-MATNR,
 WERKS LIKE EKBE-WERKS,
 BUKRS LIKE WB2_V_EKKO_EKPO2-BUKRS,
 MENGE_I LIKE WB2_V_EKKO_EKPO2-MENGE_I,
 LIFNR LIKE WB2_V_EKKO_EKPO2-LIFNR,
 COUNT TYPE P DECIMALS 4,
 BMENGE LIKE EKBE-MENGE,
 MENGE101 LIKE EKBE-MENGE,
 MENGE543 LIKE EKBE-MENGE,
 MENGE545 LIKE EKBE-MENGE,
 DIFFER LIKE EKBE-MENGE,
 TMENGE LIKE EKBE-MENGE,
 RATE LIKE EKBE-DMBTR,
 NAME1 LIKE LFA1-NAME1,
 LINE_COLOR(4),
 END OF IT_EKBE.
DATA: WA LIKE IT_EKBE.
DATA: BEGIN OF IT_FINAL OCCURS 0.
 INCLUDE STRUCTURE IT_EKBE.
DATA: END OF IT_FINAL.
DATA: BEGIN OF IT_FINAL_TEMP OCCURS 0.
 INCLUDE STRUCTURE IT_EKBE.
DATA: END OF IT_FINAL_TEMP.
DATA: BEGIN OF IT_BOM OCCURS 0.
 INCLUDE STRUCTURE CAPP_ITM.
DATA: END OF IT_BOM.
DATA: BEGIN OF IT_BOM_HEAD OCCURS 0.
 INCLUDE STRUCTURE CAPP_BOM.
DATA: END OF IT_BOM_HEAD.
*& DATA DECLARATION.
DATA: COUNT TYPE P DECIMALS 4,
 V_CNT TYPE P DECIMALS 4 VALUE '0.0001' ,
 V_MENGE LIKE EKBE-MENGE,
 V_DELETE.
TYPE-POOLS: slis.
DATA: l_date(12) TYPE c,
 l_date1(12) TYPE c,
 l_time(10) TYPE c,
 l_list(60) TYPE c.
DATA: CATALOG TYPE SLIS_FIELDCAT_ALV, "FIELDCAT
 TCATALOG TYPE SLIS_T_FIELDCAT_ALV, "IT FIELDCAT
 EVENT TYPE SLIS_ALV_EVENT, "EVENT
 TEVENT TYPE SLIS_T_EVENT, "IT EVENT
 LAYOUT TYPE SLIS_LAYOUT_ALV, "LAYOUT
 PG_TOP TYPE SLIS_FORMNAME VALUE 'TOP_OF_PAGE',
 PG_HEAD TYPE SLIS_T_LISTHEADER,
 EXIT1 TYPE SLIS_EXIT_BY_USER,
 VAR1 LIKE DISVARIANT,
 VAR2 LIKE DISVARIANT.
*& START-OF-SELECTION.
START-OF-SELECTION.
PERFORM PROCESS_SELECTION.
PERFORM DELETE_CANCELLED_DOCUMENTS.
PERFORM EXPLODE_BOM_FOR_101.
SORT IT_FINAL BY COUNT.
PERFORM DISPLAY_OUTPUT.
FREE IT_FINAL_TEMP.
*& ALV FORMATTING
*& ALV DISPLAY
PERFORM GENERATE_ALV_FIELDCAT.
PERFORM EVENTS USING TEVENT.
PERFORM TEXT USING PG_HEAD.
PERFORM ALV_SHOW.
*& FORM PROCESS_SELECTION.
FORM PROCESS_SELECTION.
SELECT
A~EBELN
A~EBELP
A~GJAHR
A~BELNR
A~BUZEI
A~BEWTP
A~BWART
A~BUDAT
A~MENGE
A~DMBTR
A~LFBNR
A~MATNR
A~WERKS
B~BUKRS
B~MENGE_I
B~LIFNR
FROM
EKBE AS A
JOIN
WB2_V_EKKO_EKPO2 AS B
ON
AEBELN = BEBELN AND
AEBELP = BEBELP_I
INTO
CORRESPONDING FIELDS OF TABLE IT_EKBE
WHERE
A~MATNR IN S_MATNR AND
A~WERKS IN S_WERKS AND
A~BUDAT IN S_BUDAT AND
A~EBELN IN S_EBELN AND
A~BELNR IN S_BELNR AND
A~GJAHR IN S_GJAHR AND
A~VGABE IN ('1', '7') AND
A~BEWTP IN ('E', 'O') AND
( A~BWART IN ('101', '545', '543') OR
( ABWART = '102' AND ABEWTP = 'E' ) ) AND
B~BUKRS = P_BUKRS AND
B~BSTYP = 'F' AND
B~BSART = 'SUBC'."AND
B~LOEKZ <> 'X'.
SORT IT_EKBE BY EBELN EBELP GJAHR BELNR BUZEI.
ENDFORM.
*& FORM DELETE_CANCELLED_DOCUMENTS.
FORM DELETE_CANCELLED_DOCUMENTS.
DELETE IT_EKBE WHERE BWART = '102' AND BEWTP <> 'E'.
LOOP AT IT_EKBE WHERE BWART = '102'.
READ TABLE IT_EKBE INTO WA WITH KEY BELNR = IT_EKBE-LFBNR.
IF SY-SUBRC = 0.
 DELETE IT_EKBE WHERE BELNR = WA-BELNR.
ENDIF.
ENDLOOP.
CLEAR WA.
DELETE IT_EKBE WHERE BWART = '102'.
ENDFORM.
*& FORM EXPLODE_BOM_FOR_101.
FORM EXPLODE_BOM_FOR_101.
CLEAR COUNT.
LOOP AT IT_EKBE WHERE BWART = '101' OR
 BWART = '543'.
IF NOT IT_EKBE-MATNR IN S_MATNR.
V_DELETE = 'X'.
ELSE.
CLEAR V_DELETE.
ENDIF.
IF V_DELETE <> 'X'.
COUNT = COUNT + 1.
IT_EKBE-COUNT = COUNT.
V_MENGE = IT_EKBE-MENGE.
MODIFY IT_EKBE.
IT_FINAL = IT_EKBE.
APPEND IT_FINAL.
ENDIF.
call function 'CABM_READ_BOM'
 exporting
 I_MATNR = IT_EKBE-MATNR
 I_WERKS = IT_EKBE-WERKS
 I_STLAL = '01'
 I_STLAN = '3'
 I_DATUV = IT_EKBE-BUDAT
 TABLES
 EXP_BOM_DATA = IT_BOM_HEAD
 EXP_ITM_DATA = IT_BOM
 EXCEPTIONS
 NO_RECORD_FOUND = 1
 OTHERS = 2
if SY-SUBRC <> 0.
MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
 WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
ELSE.
*START RK 18.06.2007
DELETE IT_BOM WHERE DATUV > IT_EKBE-BUDAT.
END : 18.06.2007
 IF V_DELETE = 'X'.
 LOOP AT IT_BOM.
 DELETE IT_EKBE WHERE MATNR = IT_BOM-IDNRK.
 ENDLOOP.
 REFRESH IT_BOM.
 ELSE.
 PERFORM CHECK_BOM_GR.
 ENDIF.
endif.
ENDLOOP.
FREE IT_EKBE.
ENDFORM.
*& FORM CHECK_BOM_GR.
FORM CHECK_BOM_GR.
DATA: WACNT TYPE P DECIMALS 4.
WACNT = COUNT.
LOOP AT IT_BOM.
READ TABLE IT_EKBE INTO WA WITH KEY EBELN = IT_EKBE-EBELN
 MATNR = IT_BOM-IDNRK.
IF SY-SUBRC = 0.
 WACNT = WACNT + V_CNT.
 WA-COUNT = WACNT.
 WA-BMENGE = IT_BOM-MENGE.
 WA-TMENGE = V_MENGE.
 APPEND WA TO IT_FINAL.
 DELETE IT_EKBE WHERE EBELN = WA-EBELN AND
 EBELP = WA-EBELP AND
 MATNR = WA-MATNR AND
 BELNR = WA-BELNR AND
 BUZEI = WA-BUZEI.
**START : ADDED BY .... KUMAR ON 14.06.2007
ELSE.
 WACNT = WACNT + V_CNT.
 WA-COUNT = WACNT.
 WA-BMENGE = IT_BOM-MENGE.
 WA-MATNR = IT_BOM-IDNRK.
 WA-TMENGE = V_MENGE.
 APPEND WA TO IT_FINAL.
**END ADDED BY .... KUMAR ON 14.06.2007
ENDIF.
CLEAR WA.
ENDLOOP.
REFRESH IT_BOM.
ENDFORM.
*& FORM DISPLAY_OUTPUT.
FORM DISPLAY_OUTPUT.
Populate color variable with colour properties
Char 1 = C (This is a color property)
Char 2 = 3 (Color codes: 1 - 7)
Char 3 = Intensified on/off ( 1 or 0 )
Char 4 = Inverse display on/off ( 1 or 0 )
 i.e. wa_ekko-line_color = 'C410'
IT_FINAL_TEMP[] = IT_FINAL[].
LOOP AT IT_FINAL.
CLEAR IT_FINAL-DMBTR.
********added by .... .... on 17.02.2007
 if it_final-bmenge < 0.
IT_FINAL-DIFFER = IT_FINAL-TMENGE * IT_FINAL-BMENGE * -1.
 else.
*********end by .... .... on 17.02.2007
IT_FINAL-DIFFER = IT_FINAL-TMENGE * IT_FINAL-BMENGE.
********added by .... .... on 17.02.2007
endif.
*********end by .... .... on 17.02.2007
IF IT_FINAL-BWART = '101'.
 IT_FINAL-LINE_COLOR = 'C210'.
 IT_FINAL-MENGE101 = IT_FINAL-MENGE.
 IT_FINAL-DIFFER = 0.
 LOOP AT IT_FINAL_TEMP WHERE BELNR = IT_FINAL-BELNR AND
 EBELN = IT_FINAL-EBELN AND
 EBELP = IT_FINAL-EBELP.
 IF IT_FINAL_TEMP-BWART <> '545'.
 IT_FINAL-DMBTR = IT_FINAL-DMBTR + IT_FINAL_TEMP-DMBTR.
 ELSE.
 IT_FINAL-DMBTR = IT_FINAL-DMBTR - IT_FINAL_TEMP-DMBTR.
 ENDIF.
 ENDLOOP.
 IT_FINAL-RATE = IT_FINAL-DMBTR / IT_FINAL-MENGE101.
 SELECT SINGLE
 NAME1
 INTO
 IT_FINAL-NAME1
 FROM
 LFA1
 WHERE
 LIFNR = IT_FINAL-LIFNR.
 IF SY-SUBRC <> 0.
 CLEAR IT_FINAL-NAME1.
 ENDIF.
ELSEIF IT_FINAL-BWART = '543'.
 IT_FINAL-MENGE543 = IT_FINAL-MENGE.
 IT_FINAL-LINE_COLOR = 'C200'.
 IT_FINAL-DIFFER = IT_FINAL-DIFFER - IT_FINAL-MENGE543.
 CLEAR: IT_FINAL-LIFNR,
 IT_FINAL-EBELN,
 IT_FINAL-BELNR,
 IT_FINAL-MENGE_I,
 IT_FINAL-BUDAT.
ELSEIF IT_FINAL-BWART = '545'.
******added by .... on 17.02.2007
 IT_FINAL-MENGE = IT_FINAL-MENGE * -1.
 IT_FINAL-MENGE = IT_FINAL-MENGE.
*******end by .... on 17.02.2007
 IT_FINAL-MENGE545 = IT_FINAL-MENGE.
 IT_FINAL-LINE_COLOR = 'C200'.
 IT_FINAL-DIFFER = IT_FINAL-DIFFER - IT_FINAL-MENGE545.
 CLEAR: IT_FINAL-LIFNR,
 IT_FINAL-EBELN,
 IT_FINAL-BELNR,
 IT_FINAL-MENGE_I,
 IT_FINAL-BUDAT.
ELSE.
 IT_FINAL-LINE_COLOR = 'C200'.
 CLEAR: IT_FINAL-LIFNR,
 IT_FINAL-EBELN,
 IT_FINAL-BELNR,
 IT_FINAL-MENGE_I,
 IT_FINAL-BUDAT.
ENDIF.
MODIFY IT_FINAL.
ENDLOOP.
ENDFORM.
*& Form GENERATE_ALV_FIELDCAT
 text
FORM GENERATE_ALV_FIELDCAT.
DATA: POS TYPE I.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'COUNT'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'S. No.'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'MATNR'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Mat. No.'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'BMENGE'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'BOM Qty'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'EBELN'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'PO No.'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'MENGE_I'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'PO Qty'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'BELNR'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Gr. No.'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
CATALOG-HOTSPOT = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'BUDAT'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'GR Date'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'MENGE101'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = '101 Gr Qty'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'MENGE543'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = '543 Gr Qty'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'MENGE545'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = '545 Gr Qty'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'DIFFER'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Difference'.
CATALOG-NO_ZERO = ' '.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'LIFNR'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Vendor'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'NAME1'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Vendor Name'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'RATE'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Rate'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
POS = POS + 1.
CLEAR: CATALOG.
CATALOG-COL_POS = POS.
CATALOG-FIELDNAME = 'DMBTR'.
CATALOG-TABNAME = 'IT_FINAL'.
CATALOG-SELTEXT_L = 'Value'.
CATALOG-NO_ZERO = 'X'.
CATALOG-FIX_COLUMN = 'X'.
APPEND CATALOG TO TCATALOG.
ENDFORM.
*& Form ALV_SHOW
 text
FORM ALV_SHOW.
LAYOUT-COLWIDTH_OPTIMIZE = 'X'.
LAYOUT-BOX_TABNAME = 'IT_FINAL'.
LAYOUT-INFO_FIELDNAME = 'LINE_COLOR'.
LAYOUT-ZEBRA = 'X'.
CALL FUNCTION 'REUSE_ALV_GRID_DISPLAY'
 EXPORTING
 I_CALLBACK_PROGRAM = SY-REPID
 I_CALLBACK_USER_COMMAND = 'USER_COMMAND'
 IS_LAYOUT = LAYOUT
 IT_FIELDCAT = TCATALOG
 IS_VARIANT = VAR1
 I_SAVE = 'A'
 IT_EVENTS = TEVENT[]
 TABLES
 T_OUTTAB = IT_FINAL.
ENDFORM . "ALV_SHOW
*& FORM USER_COMMAND.
FORM USER_COMMAND USING
 R_UCOMM LIKE SY-UCOMM
 SELFIELD TYPE SLIS_SELFIELD.
DATA: TABIX LIKE SY-TABIX,
 WA LIKE IT_FINAL.
TABIX = SELFIELD-TABINDEX.
READ TABLE IT_FINAL INTO WA INDEX TABIX.
IF NOT WA-BELNR IS INITIAL.
set parameter id : 'MBN' FIELD WA-BELNR.
CALL TRANSACTION 'MB03' AND SKIP FIRST SCREEN .
ENDIF.
ENDFORM.

Hi,
U can try this standard report for subcontracting:
J1IFR (Transaction name),
Not sure how much this will be useful to u.
regards,
Viji

Oracle Projects Differences from 11i to R12

Hello All,
Currently we are upgrading from 11.5.10.2 to R 12.1.3
We have oracle projects implemented in 11i.
I am researching to get the differences occurred in oracle projects functional and technical from 11i to R12
It will be a great help to us if we could get some documents or a link which shows the differences.
Thanks and Regards,
Ankit Vishwakarma

Project new features
Oracle Project Foundation
New Concurrent Process
ADM: Purge Obsolete Projects Data
Oracle Project Costing
Federal Budgetary Accounting for Project Expenditures via Subledger Accounting
Contingency Worker Clearing Projects to allow CWK to charge multiple projects
Additional Project Information in Oracle Time and Labor (Project Name and Task Name)
Federal Budgetary Accounting for Project Revenue
Additional journal entries are available in Subledger Accounting for the required Federal Budgetary entries.
Date Effective Funds Consumption
Project Type option that requires cost and event transaction dates to fall within the agreement start and end dates.
Transactions are only billed against the agreement if the entire transaction amount can be funded (no partial recognition) for both revenue and invoicing.
Without enabling this option, revenue generation supports partial billing for transactions.
New Parameters for MGT: Invoice Review
Project Status
Project Closed After Date
Project Range
New Parameters for MGT: Unbilled Receivables Aging
Project Status
Project Closed After Date
Project Range
Oracle Project Management New Audit Process for Project Performance Reporting Setup
AUD: Project Performance Reporting Setup
New Parameters for Refresh Project Performance Data Process
Actual or All Amounts (Plan and Actual)
Workplan Version
Financial Plan Version
Workplan EnhancementsAbility to Delete Published Workplan Versions (except the latest published version, baseline version, and workplan versions included in a program hierarchy) Usability Enhancements
Update Work Breakdown Structure page is now obsolete.
View, maintain, and update a workplan structure from the Update Tasks page.
Where no latest published workplan version exists, the current working version displays on the Update Tasks page when navigating to the Workplan Tasks.
Indent or outdent multiple workplan tasks in a single step.
Confirmation, information, and warning messages appear on HTML pages during Apply Latest Progress as well as the Submit Progress processes. Messages include status information during processing and the availability of the latest progress information.
New Public API for Creating, Maintaining, and Deleting Programs New set of public API procedures:
Designate a project as a program and indicate whether projects linked to the program can belong to multiple programs.
Create links from a program to one or more projects
Update links from a program to one or more projects
Delete links from a program to one or more projects
Budgeting And Forecasting Enhancements Enhanced Automatic Calculation and Derivation Logic
For plan lines that do not have a specified a quantity, the amount is no longer copied to the quantity field with the rate value set to 1.
Rate now has a lower precedence than quantity and amount in automatic calculations. The rate will be re-derived when the quantity, rate and amount are entered at the same time for a plan line.
When the burden multiplier is overridden by updates to the raw cost or burden cost, subsequent calculations of the burden cost will use the override burden multiplier. The same is true when the markup percent is updated by changes to plan line components: the override markup percentage will be used in revenue calculations.
Enhanced Handling of Override Rates on Budget / Forecast Lines
Override rates for a planning transaction on Edit Budget and Edit Forecast pages.
o Raw Cost Rateo Budened Cost Rateo Bill Rate
Override rates are applied to all existing and new periodic lines for the planning transaction.
Average rates fields on these pages are now disabled for entry and are used for display only.
Simplified Addition of Planning Elements and Resources
New but unbudgeted tasks and resources can be added to a budget or forecast version.
Add either all new tasks and planning resources or new tasks only to the current plan version.
Self Service Expenditure Inquiry
Ability to drill into expenditure details from the Financials tab.
Reporting Pack for Generation and Distribution of XML Publisher Reports
A reporting pack is a set of report templates and recipients by project role.
The Generate Reporting Pack concurrent program emails the reports generated from the report templates based on pre-defined intervals.
The report template establishes each report’s layout and content.
New reports templates are configured using XML Publisher tools.
New or modified reports can be added to an existing reporting pack or be used to create an entirely new report set.
Predefined data definition files that contain XML tags for performance measures and project data are provided.
Predefined Reports:
Project Change Document Report
Project Committed Cost Report
Project Cost Detail Report
Project Cost Labor Report
Project Cost Summary Report
Project Earned Value Report
Project Financial Summary Report
Project Forecast Summary Report
Project Revenue At Risk Report
Budget Integration with Federal Budget Execution and/or 3rd Party Budget
The budget integration workflow supports integration with the Federal Budget Execution module..
The workflow can be customized to interface budget lines to external budgeting applications.
Microsoft Project 2007 Certification
Integration with Microsoft Project 2007 is supported.
Project Performance Reporting: Additional MeasuresYTD, QTD and At Completion calculated measures are available on the following pages:
Performance Overview Period-to-Date
Summary/Analysis
Task Summary/Analysis Resource Summary/Analysis
Project Performance Reporting: Inter-Project Revenue / Billing AmountsInter project revenue / billing amounts are available on the following pages:
Project List View Workplan Cost
Exception Reporting Performance Overview
Task Summary/Analysis Resource Summary/Analysis
Period-to-Date Summary/Analysis
Supplier Cost DashboardSubcontractor Payment ControlsSupport for Pay when Paid Scenarios
A new “Pay when Paid” payment term for subcontracts automatically places holds on all subcontractor invoices under that subcontract until the corresponding customer payment is received.
Subcontract Payment Controls workbench allows project manager to manage the holds, with visibility into both the customer invoices and the related subcontractor invoices.
Workflow notifications about the receipt of the customer payment allow the project manager to automatically or manually release the subcontract invoice.
Associations between the customer invoices and the subcontractor invoices may be automatically maintained based on the billing of project expenditures for cost-plus contracts, or may be manually maintained for fixed price contracts.
Payment Controls for Subcontract Deliverables
Support for the tracking and monitoring of subcontract deliverables that place automatic holds on subcontractor invoices in the case of noncompliance.
Oracle Procurement Contracts allow a subcontract administrator to specify payment impact controls that will take effect when a subcontract deliverable is not met.
From the Subcontractor Payment Controls workbench, the project manager can view a checklist of the all the current subcontract deliverables, to assist in evaluating the subcontractor status prior to releasing monthly progress payments.
Oracle Project Resource ManagementResource Search Enhancements
Resource Search by Email Address
Resource Search by Person Type
Streamlined Navigation on Staffing Home
Cross Validation of Project and Assignment Dates
Requirement start dates are equal to or greater than the project start date and less than the project end date and that finish dates are equal to or less than the project end date but greater than the project start date.
Assignments cannot be added beyond the project end date.
A project team role end date cannot be beyond the project end date. If the roles are created before the project end dates are entered, users will receive an error if they later try to enter an end date that is earlier than the end date for existing roles.
When project transaction dates are moved corresponding assignment dates are validated against the new project dates. If the new project transaction dates fall outside the dates for existing assignments, users are given an option to shift the assignment dates or cancel the date adjustment.
Defaulting of Work Patterns’ From and To Dates
Work pattern from and to dates will default from the requirement start and end dates.
Improved Exception Handling of Maintain Project Resources Process
PRC: Maintain Project Resources delivers improved exception handling and notification when it encounters errors while processing employee records.
New Public APIs for Resource ManagementThe new PJR APIs fall into the following four categories:
Requirement Public APIs
Assignment Public APIs
Candidate Public APIs
Competence Public APIs
Organization Authority: Obsolete Forecast Authority
Removes the forecast authority functionality from the organization authority form
Removes existing security data relating to forecast authority.
Replaces the PJR forecast functionality with the new HTML based forecasting functionality. The new forecasting functionality has its own security mechanism and does not honor the old forecast authority model.
Improves the performance of security calls to organization authority because the existing security data is being removed.
Oracle Grants AccountingAward Budgeting Enhancements Budget period validations
Budget periods will not be validated across award budgets when those awards fund a single project.
Flexibility to establish award budgets based on the actual duration of the award, while not being confined based on the existing budgets already established for the project.
Automatic summarization of project budgets
With the new budget period validations, automatically summarize to a project budget viewable in Project Status Inquiry.
Two profile options have been added to identify the budget entry methods that will be used to summarize the project budgets.
Budget Line Sorting Option
Sort budget lines by Resource name, or by effective dates for budgets with date range periods. Provides the flexibility to view the budget lines by period or by budgeted resource.
Award Status Inquiry Enhancements View by budget period
Allows the Find Award Status window to be limited to a single period, range of periods, or inception to date for a particular award.
Reflects the budget periods entered on the award budget.
GL and PA Date Parameters on Find Expenditure Items window
GL and PA date parameters have been added to the Find Expenditure Items window.
GL Date Parameters on Find Commitments window
GL Date parameters have been added to the Find Commitments window.
KKG

Account postings in GR & IR for Subcontracting

Hi Experts,
I need to know the account postings for both GR & IR during Sub contracting.
Let us take the scenario . .
PO price - 1000(Gross) + 200(Tax) = 1200 (Net) for 1 Qty
GR - PO Net Price due to Moving Average price.
IR - 1200(Gross) + 240 (Tax) = 1440
Please explain the accounting entries during Goods Receipt and Invoice Receipt.
By
Prabhu

If Material has Price Control as "V" (MAP)
(BSX) Stock A/c of Assembly - Dr
(BSV) Change in Subcon Stock - Cr
(FRL) Subcontracting Charges - Dr
(WRX) GR/IR Clearing A/c - Cr
(BSX) Stock A/c of Components - Cr
(GBB-VBO) Consumption A/c of Components - Dr
If Material has Price Control as "S" (Std. Price)
If Material is having Price Control as "S" then Price Difference A/c will also in picture.
This depends on configuration; SPRO > MM > Inventory Management and Physical Inventory > Goods Receipt > Price Differences for Subcontract Orders at Goods Receipt
Price Differences for Subcontract Orders at Goods Receipt
In this step, you configure for each valuation area whether price differences are generated for a Subcontract order at the time of a goods receipt if the manufactured material is managed at standard price and the standard price varies from the receipt value (externally performed service + value of components + delivery costs).
Example
Finished product: $400 (value at standard price)
Subcontract order:
o Ext. service : $250
o Components : $100
Posting schema without price differences:
Stock account FERT : 400 +
Stock change : 400 -
GR/IR clearing acct : 250 -
External service acct : 250 +
Compon. stock account : 100 -
Consumption account : 100 +
Posting schema with price differences:
Stock account FERT : 400 +
Stock change : 350 -
Price difference : 50 -
GR/IR clearing acct : 250 -
External service acct : 250 +
Compon. stock account : 100 -
Consumption account : 100 +
hope it help

Issue Price Difference Acct. in JE of goods return

Dear all,
There is issue in price difference account(Defined as Material Purchase Gain A/c in warehouse)
in good return journal entry,
Eloborating problem : User booking subcontracting grpo for qty 1470.024 with price also for 1470.024,
JE for GRPO is Sub Contracting Charges A/c Dr to Sub Contracting Charges Clearing A/c Cr.
ie.,
Sub Contracting Charges a/c Dr -11,92,189.46
Sub Contracting Charges Clearing A/c Cr -11,92,189.46
Now they partially do good return for qty 811 with price 1470.024,
JE for Goods return is
Material Purchase Gains A/c Dr -11,78,900.46
Sub Contracting Charges a/c Dr -13,289
Sub Contracting Charges Clearing A/c Cr -11,92,189.46
Actually sub contracting charges a/c should have been debited to 11,92,189.46,
Why it is hitting Material purchase gains a/c ?
Pl clarify it.
Edited by: Jeyakanthan A on May 21, 2009 3:26 PM

Hai!
As per my understanding,
Stock Acc always in Asset Draw, Price Diff Acc in Expense Draw.
For Example..
1.I am purchasing a item of 10 qty each 1 rupee through GRPO.
2.It will post a JE like stock acc INR 10 Debit and GRNI Acc 10 Credit.
3.After that i have transfered my 5 qty to some other warehouse.
4.I am booking a AP invoice with that GRPO as base, now i have changed my price to 2 rupee.
5.It will post a JE like stock acc INR 5(51 which like in warehouse) debit, GRNI Acc INR 10 debit, price Diff Acc INR 5 Debit (51 go as expence) and Vendor INR 20 Credit.
Regards,
Thanga Raj.K

Problem in Posting of GR for Subcontracting PO Through MIGO

Hi All,
When I am posting 101 through MB01 for Subcontracting PO The system is creating three line items in Material Document( 101, 543 & 545 ) which is correct.
But if i am doing the same through MIGO it is posting three line items as (101, 543 & 543) - Which is wrong.
I am using SAP R/3 4.7.
Please let me know if there is any OSS note to fix this.
Thanks a ton in advance.
-Nirupam

Hi,
I can't belive it....543 is showing Credit indicator and 545 is showing debit indicator. Which is perfect. So, when we receive a subcontracting PO, if at all there is any byproduct that is going to be received, it has to be either debit or credit (only one way) whether we receive from MB01 or MIGO. If you see 545 in MB01 that means, you are receiving by-products along with ....However, in MIGo you are showing only 543 (consumption of components).....Are you missing any by-products comingup in mIGO? Is the PO the same you are using in both MB01 and mIGO....very minimal differences in terms of functionality we may encouner between these two transactions but I strongly doubt about posting two different movements types for exactly the same data....I am not doubting you; just curious to work on such problem. Please cross verify again and let me know.
Regards

Subcontract goods receipt without components withdrawal.

Hi,
we're noticing many occurrences of this problem since we've upgrade to ECC 6.0.
Too often we encounter GR of subcontracting PO's that doesn't consumed all components existing at the "Components Overview".
Besides the common reasons for this (untic the item or setting the quantity to zero), do you know any other?
Best Regards,
André Costa

no no no... I check the material document after GR post.
Every time I test, all components appear at MIGO. But, somehow, when it's the people from the warehouse, something happens that I can't figure out.
We do periodic inventories to the subcontractors, and after that we check the SAP stock against what's reported. When I get a big difference, I start checking the GR for all PO's and I find some lacks of components withdrawal.
I can't tell you if at MIGO there are all components or not, because I'm not there to see.
They say, they never reset a quantity nor untic an item.
We use Purchase Orders.
André Costa

Subcontract order component delivery Error

Hi..
I have created a Subcontract PO for disposing a material .Vendor will cahrge me for disposal services provided.
i will provide material to b disposed as compnents with subcontract PO.
i have 2 subcontarct POs for 2 different POs.
For 1 PO , vendor is charging me for the service provided . for this PO, i can crate delivery thr' ME2O and Subsequent GI andGR.
For Other PO , i have checked Free goods check box.
for this PO when i try to create Delivery thruogh 'Me2O, shipping point is not getting populated and , i am getting error 'Essential transfer parameters are missing in record: 000001'
so i want to know where this shipping point and free goods indicer are linked.
why this error is not occuring for earleir PO . Difference in both POs is that only venodr in different and one is free PO other is valuated.
Thanks in advance

hi akkshay..
i think u did not understand my problem.
my problem is that shipping point is no getting populated in ' Me2O' while creating delivery. also this field is greyed out. so cant do that manually also.
in SPRO , i have maintained teh combination of shipping condition, loading group, plant and shipping point
so where is the problem and how it can be tackled.
thanks in advance

Issue Storage Location in Components details Subcontracting PO

Hi all
I need to implement this process in SAP:
I have to send material X, from storage location B 'broken', to my supplier for repairing. After He has repaired it I post good recipe of material X in the storage location A 'adjusted'.
I plan material X through MRP at plant level only for storage location A.
In the material master I've set procurement type 'F' and Special Procurement '30'.
I created a recursive BOM for material X where I entered, for component X, B as issue storage location.
In this way MRP run (with '1' as value of 'Create PR' parameter) creates subcontracting PR with X as material to buy and X as component to send to vendor, but in the detail of component I have the storage location field kept empty.
This for me is a problem.
In fact when I create PO from this PR automatically through ME59 transaction, the System creates a requirement at plant level for component X.
But this requirement is for broken material and has to be covered by stock in storage location B.
I know that is not easy to understand all the details of this process, even due to my english, but I hope someone can help my.
Please if you need a clear up, ask me.
Thanks for your help
Yours faithfully
Paolo Verderio

Hi Paolo,
don't worry. Your explanation is well understandable.
I cannot advise how to fix the problem with the missing storage location. I just have some doubts that it is the right approach to distinguish between an boken and a repaired material by storage location. Even for stock valuation there is certainly a difference between both, that you can't make transparent by storage location, and also if you look at your available stocks.
I would recommend to have either different materials or different valuation types. I have to confess that I am not sure that valuation types would help for your subcontracting PO.
best regards,
Udo

Purchase price variance in subcontracting order

Our customer has the following scenario:
     Purchase account is posted with the value of stock subsequently purchase price variance is a legal account
     Material ledger is active
     Inventories are managed with standard price for each material code
     Latin method management of inventories post stock values on managerial account
In good receipt with a subcontracting order, in case of purchase price variance, legal account of purchase price variance is posted generating a wrong reconciliation between managerial and legal posting.
Example
The subcontractor is a co packer that assembles material A to produce material B
Material A has a standard price of   3
Material B has a standard price of     5
If Co packer fees have a value     of     2 no purchase price variance occurs during good receipt, as a matter of fact :
(Co packing fees) 2 + (Material A) 3 = (Material B) 5
Else if co packer fees have a value of 3 a purchase price variance of 1 occurs and itu2019s posted using transaction key u201CPRDu201D. On FI the following document is posted:
Legenda : L stands for legal account , M stands for managerial account
(L) Co packing Fees                                         3
(L) Invoice to receive                                     3
(L)Purchase price variance                            1
(M) Consumption Material A                           3
(M) Stock Material              A                            3
(M) Stock Material               B                            5
(M) Production Confirmation Material B       6
In this scenario Purchase price variance should be a managerial account, but transaction key is PRD and changing the account would affect every posting.

This is the answer from OSS
Dear Customer,
the system works as designed.
When Material Ledger is activated, price differences are always
generated under the circumstances you have described. The reason is
that when material ledger is activated, price differences must not be
included into the stock changes value, otherwise the system would
not be able to calculate an actual price.
When Material Ledger is activated, the customizing setting
for handling price differences in the subcontracting process has no
effect.
Best regards,
Santiago Lorite
AGS Primary Support, Business Suite & Technology u2013 Logistics

Difference between Delivery, Sales order and Shipment

Hi
I would like to know difference between sales document, delivery document and shipment.
When is the delivery created? What data will it have?

Hi
Sales Documents 
Sales-related business transactions are recorded in the system as sales documents. These are grouped into four categories:
Pre-sales documents: inquiries and quotations
Sales orders
Outline agreements, such as contracts and scheduling agreements
Customer problems and complaints, leading to free-of-charge deliveries and credit memo requests
If your particular business processes require it, you can process deliveries and billing documents directly from a sales document. In addition, some sales documents, such as cash sales and rush orders automatically trigger the creation of subsequent delivery and billing documents.
Basic Functions Within Sales Order Processing
During sales order processing, the system carries out basic functions, such as:
Monitoring sales transactions
Checking for availability
Transferring requirements to materials planning (MRP)
Delivery scheduling
Calculating pricing and taxes
Checking credit limits
Creating printed or electronically transmitted documents (confirmations and so on)
Delivery Processing
In its role as central object of the goods issue process, the outbound delivery supports all shipping activities including picking, packing, transportation and goods issue. During the outbound delivery process, shipping-planning information is recorded, status of shipping activities is monitored and data accumulated during shipping processing is documented. When the outbound delivery is created, the shipping activities, such as picking or delivery scheduling, are initiated, and data that is generated during shipping processing is included in the delivery.
Range of Functions
An outbound delivery can be created as follows:
With reference to a sales order
With reference to a stock transport order
With reference to a subcontract order
Shipping 
Shipping is an important part of the logistics chain in which guaranteed customer service and distribution planning support play major roles.
In shipping processing, all delivery procedure decisions can be made at the start of the process by
Taking into account general business agreements with your customer
Recording special material requests
Defining shipping conditions in the sales order
The result is an efficient and largely automatic shipping process in which manual changes are only necessary under certain circumstances.
Integration
The Shipping component is integrated under the Logistics Execution component. Shipping is a subsequent activity of the Sales component.
Range of Functions
The shipping module supports the following functions, which include but are not limited to:
Deadline monitoring for reference documents due for shipment (sales orders and purchase orders, for instance)
Creating and processing outbound deliveries
Planning and monitoring of worklists for shipping activities
Monitoring material availability and processing outstanding orders
Monitoring the warehouse's capacity situation
Picking (with optional link to the Warehouse Management system)
Packing deliveries
Information support for transportation planning
Support of foreign trade requirements
Printing and transmitting shipping documents
Processing goods issue
Controlling using overviews of
 o Deliveries currently in process
 o Activities that still are to be carried out
 o Possible bottlenecks

Subcontracting PO - GR/IR difference

Similar Messages

Maybe you are looking for