Subcontracting modified

Hi
But when we receive the finished goods after subcontracting by 101
We will update the system with the consumption of the component materials provided to the subcontractor.it will be automatically done by movement type 543. Suppose we are having 3 components in for that finished product, Our user has entered only 2 components means he has not ticked 3rd item so that it is left, and posted succesfully. And that PO is closed. but finished quantity he has entered correct. Again if i go for MIGO to enter that same PO message coming that PO does not contain any selectable items. Now our requirement is how to post that remaining components?
Thank you
Rehan

Hi,
For consumption of components by movement type 543, all the components are selected by default. Pl. check why the user has removed the tick.
Now the material consumption has to be manually enter against other cost object (For example - Sale Order / Cost Center) manually in transaction MB1A. For this bring the material to your plant vide transaction MB1B (Mvt. Typ - 542) & then post the consumption.
Regards,
Prashant

Similar Messages

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

Open Po quantity in subcontracting Purchase Order

Hi,
In case subcontracting purchase order,If order quantity 10 and recept quantity is 05 then in delivery shedule tab I didn't got any open purchase order quantity means 05 quantity why?
Thanks and Regards
Anil Patil

Hi Anil.
Please check the following fields in schedule line:
- 'Scheduled qty': 10
- 'Delivered' (quantity): 5
(This means the goods were partially delivered for the PO)
If your situation is this you don't have to expect SAP to create new shedule line I think.
I think you have to modify the schedule line manually if you want a 'Delivery date' different from that was defined in the line of the PO item.
BR
Csaba

Goods receipt for subcontracting order! BAPI_GOODSMVT_CREATE

I wanna use BAPI "BAPI_GOODSMVT_CREATE" to create goods receipt for subcontracting order.
But it says that this combination is not possible. Combination of my movement type and this BAPI.
What can i do to solve it?
thanks in advance.

>
Julia Nikiforva wrote:
> I wanna use BAPI "BAPI_GOODSMVT_CREATE" to create goods receipt for subcontracting order.
> But it says that this combination is not possible. Combination of my movement type and this BAPI.
>
> What can i do to solve it?
>
> thanks in advance.
Might work
report zbapi_goodsmovement.
parameters: p-file like rlgrap-filename default
'c:\sapdata\TEST.txt'.
parameters: e-file like rlgrap-filename default
'c:\sapdata\gdsmvterror.txt'.
parameters: xpost like sy-datum default sy-datum.
data: begin of gmhead.
include structure bapi2017_gm_head_01.
data: end of gmhead.
data: begin of gmcode.
include structure bapi2017_gm_code.
data: end of gmcode.
data: begin of mthead.
include structure bapi2017_gm_head_ret.
data: end of mthead.
data: begin of itab occurs 100.
include structure bapi2017_gm_item_create.
data: end of itab.
data: begin of errmsg occurs 10.
include structure bapiret2.
data: end of errmsg.
data: wmenge like iseg-menge,
errflag.
data: begin of pcitab occurs 100,
ext_doc(10), "External Document Number
mvt_type(3), "Movement Type
doc_date(8), "Document Date
post_date(8), "Posting Date
plant(4), "Plant
material(18), "Material Number
qty(13), "Quantity
recv_loc(4), "Receiving Location
issue_loc(4), "Issuing Location
pur_doc(10), "Purchase Document No
po_item(3), "Purchase Document Item No
del_no(10), "Delivery Purchase Order Number
del_item(3), "Delivery Item
prod_doc(10), "Production Document No
scrap_reason(10), "Scrap Reason
upd_sta(1), "Update Status
end of pcitab.
call function 'WS_UPLOAD'
exporting
filename = p-file
filetype = 'DAT'
IMPORTING
FILELENGTH =
tables
data_tab = pcitab
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
OTHERS = 6
if sy-subrc <> 0.
message id sy-msgid type sy-msgty number sy-msgno
with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
exit.
endif.
gmhead-pstng_date = sy-datum.
gmhead-doc_date = sy-datum.
gmhead-pr_uname = sy-uname.
gmcode-gm_code = '01'. "01 - MB01 - Goods Receipts for Purchase Order
loop at pcitab.
itab-move_type = pcitab-mvt_type.
itab-mvt_ind = 'B'.
itab-plant = pcitab-plant.
itab-material = pcitab-material.
itab-entry_qnt = pcitab-qty.
itab-move_stloc = pcitab-recv_loc.
itab-stge_loc = pcitab-issue_loc.
itab-po_number = pcitab-pur_doc.
itab-po_item = pcitab-po_item.
concatenate pcitab-del_no pcitab-del_item into itab-item_text.
itab-move_reas = pcitab-scrap_reason.
append itab.
endloop.
loop at itab.
write:/ itab-material, itab-plant, itab-stge_loc,
itab-move_type, itab-entry_qnt, itab-entry_uom,
itab-entry_uom_iso, itab-po_number, itab-po_item,
pcitab-ext_doc.
endloop.
call function 'BAPI_GOODSMVT_CREATE'
exporting
goodsmvt_header = gmhead
goodsmvt_code = gmcode
TESTRUN = ' '
IMPORTING
goodsmvt_headret = mthead
MATERIALDOCUMENT =
MATDOCUMENTYEAR =
tables
goodsmvt_item = itab
GOODSMVT_SERIALNUMBER =
return = errmsg
clear errflag.
loop at errmsg.
if errmsg-type eq 'E'.
write:/'Error in function', errmsg-message.
errflag = 'X'.
else.
write:/ errmsg-message.
endif.
endloop.
if errflag is initial.
commit work and wait.
if sy-subrc ne 0.
write:/ 'Error in updating'.
exit.
else.
write:/ mthead-mat_doc, mthead-doc_year.
perform upd_sta.
endif.
endif.
FORM UPD_STA *
form upd_sta.
loop at pcitab.
pcitab-upd_sta = 'X'.
modify pcitab.
endloop.
call function 'WS_DOWNLOAD'
exporting
filename = p-file
filetype = 'DAT'
IMPORTING
FILELENGTH =
tables
data_tab = pcitab
EXCEPTIONS
FILE_OPEN_ERROR = 1
FILE_READ_ERROR = 2
NO_BATCH = 3
GUI_REFUSE_FILETRANSFER = 4
INVALID_TYPE = 5
OTHERS = 6
endform.

EKET-FIXKZ set after partial goods receipt of subcontract delivery schedule

Dear all,
when booking a partial goods receipt (via MIGO) of the finished product of a subcontract delivery schedule the schedule line becomes fixed (EKET-FIXKZ = 'X'), which hinders the next MRP run to modify the delivery schedule according to the new requirements.
I have tested to change the fixing indicator via SE16 and the next MRP run will then replan the sub contract delivery schedule correctly. But this is no solution.
Is there a way to modify this setting via an EXIT or BADI in MIGO ?
Many thanky for your help
Rabanus Diehl

Dear all,
when booking a partial goods receipt (via MIGO) of the finished product of a subcontract delivery schedule the schedule line becomes fixed (EKET-FIXKZ = 'X'), which hinders the next MRP run to modify the delivery schedule according to the new requirements.
I have tested to change the fixing indicator via SE16 and the next MRP run will then replan the sub contract delivery schedule correctly. But this is no solution.
Is there a way to modify this setting via an EXIT or BADI in MIGO ?
Many thanky for your help
Rabanus Diehl

Sending components on a PM03 task for subcontracting

Hi,
Is it possible to send components on a PM03 (external services) operation for subcontracting?
To be more clear: we've defined the following starting scenario's:
1) send an item for an analysis - positiontype L / PM02 operation
2) send an item for a modification directly - position type L / PM02 operation
Ad1:
The subcontractor might report back that the item sent needs to be overhauled or should be modified. In any way, a certain service (modification) should be carried out. This service is predefined in the system in a service master record. We currently process this service as a PM03 operation in the PM order and stipulates a service preq and PO. So send the item on PM02, add another line - PM03 - to handle to service. We do a GR on the PM02 operation and do a service entry sheet receipt for the service performed.
Ad2)
The item will be modified and shipped back. Only PM02 is applicable and only a GR will be performed.
The service / modification will be handled as a PM03 operation as the item is already at the subcontractor. Would it also be possible to only use a PM03 and add send the item on this PM03 operation as well? I.e. somehow combine position type S and L?
Or would material type Service (DIEN) be suitable for this?
Thanks for the suggestions.

Hi,
Is it possible to send components on a PM03 (external services) operation for subcontracting?
To be more clear: we've defined the following starting scenario's:
1) send an item for an analysis - positiontype L / PM02 operation
2) send an item for a modification directly - position type L / PM02 operation
Ad1:
The subcontractor might report back that the item sent needs to be overhauled or should be modified. In any way, a certain service (modification) should be carried out. This service is predefined in the system in a service master record. We currently process this service as a PM03 operation in the PM order and stipulates a service preq and PO. So send the item on PM02, add another line - PM03 - to handle to service. We do a GR on the PM02 operation and do a service entry sheet receipt for the service performed.
Ad2)
The item will be modified and shipped back. Only PM02 is applicable and only a GR will be performed.
The service / modification will be handled as a PM03 operation as the item is already at the subcontractor. Would it also be possible to only use a PM03 and add send the item on this PM03 operation as well? I.e. somehow combine position type S and L?
Or would material type Service (DIEN) be suitable for this?
Thanks for the suggestions.

Creating delivery notes for providing material to vendor (subcontracting)

Hi,
I am pretty new in the PP module of SAP, and have a general question regarding the subcontracting process for single operations in a production order.
Assuming the raw material has id A and the final material has id B. My routing consists of several operations that have to be performed to transform A into B. One of the operations has to be done with subcontracting (key PP02), and the system creates the purchase requisition / purchase order for it. I have operations before and after it.
Now I need to send the parts to the vendor, and want to create some kind of delivery notes (paper), which helps controlling the shipping etc., how can I do this? All I have right now is the purchase order, which does not contain any information about the material, but only about the service to be performed by the vendor.
I already thought about assigning a bom for providing material in the purchase order. But then I would need a material ID for the semi-final part which is somewhere between A and B and would need to have it on stock.
What is the standard way of doing this?
Thanks in advance!
Kind regards!
Daniel

Hi Nandha!
Thanks for your quick response.
If I check the "Subcontracting" button on the tab Ext. processing in the production order, I need to assign components in the purchase order which will be provided to the vendor. These components either have to be on stock, or would be processed by MRP and planned orders would be created. That is not what I need.
I have only one single part which consists of a raw material and only gets modified by the operations. No other component will be added at the vendor. So which material ID should I assign to the purchase order in order to just send the semi-finished pieces to the vendor? I cannot assign the raw-material again, because it would create another demand in the MRP again! I also cannot put the semi-finished parts on stock, because I don't have a material id for the part in this status.
Thanks & regards!
Daniel

Rework in Subcontracting Process

Hi Experts,
I need some suggestion for below scenario,
Finished product has been produced from subcontract vendor. Afterthat partial qty of the FG identified rejected. Now we
need to send it again for rework. In the rework process
vendor change some of the rawmaterial's.
Eg:
Finished Goods : FG1
Raw material used : 1) RAW1 2) RAW2 3)RAW3 4)RAW4
PO Qty : 50
Delivered : 50
Rej Qty : 20
Now, In the rework process subcontract vendor need to change
only RAW1 & RAW2. He can use old RAW3 & RAW4.
Hope my explaination is clear.
How this scenario mapped in SAP ?
Pl suggest.
RRS.

Hi,
You van issue a new PO for four FG and when it's ready please modify the PO's component list (maybe it is on 'Material' tab...or on one of the tabs at item level).
Please modify the component list:
- remove RAW3&4
- put FG among the component
(RAW1&2 should be on the component list as default)
In this case you will post RAW1&2 and FG to your SC Vendor and you will get FG via mvt 101 and you will consume RAW1&2 and FG via mvt 543.
The question is who and how covers the cost...
BR
Csaba

PPV for subcontracting materials mystery- posting to a different cost element?

Dear All:
Are there any OBYC (FI-MM) account determination settings to have PPV incurred due to Subcontract (SC) POs post to a different account than regular PPV? If not, is there any distinguishing characteristic at the line item level for SC PPV posting to report it in contrast with regular PPV line item?
Or am I looking at creating a substitution rule to make this happen?
Looking forward to some insights!

Hi Althea and Szymon: Thank you for your inputs. The subcontract material in our system is setup as F/30 (Procurement Type, Special Procurement) and as a HALB (semi-finished goods) in the same plant as other semi finished goods. So, no opportunity to segregate their PPV (posted via MT 101) account via valuation modifier in OBYC.
BSV transaction is used to store the offsetting account during inventory receipt during 101. So, in essence here's an example of accounting doc during GR :
Description       Amount   Transaction     Material      Quantity
FG Inv (B/S)        100          BSX              FG123            +1
GR/IR (B/S)         -15          WRX            FG123            -1
PPV (P/L)            -25          PRD            FG123             -1
SFG Cons (P/L)   -75          BSV            FG123              -1
Subc Fee (P/L)     15           FRL            FG123             +1
Inv SFG (B/S)       -12          BSX           SFG456           -1
SFG Cons (P/L)    12         GBB-VBO    SFG456           +1
So BSV+PRD = BSX (FG)
I am looking to see if I can get the $25 favorable PPV posted to some other account via OBYC. Right now it's getting posted through PRD and getting mixed up with PPV for external purchases.
Thanks for your inputs.

Subcontract Service PO Help

Dear all,
I have doubts in creating subcontract service PO. Here is my scenario. I have a project going on which i hire subcontractors to perform the planned activities. Thus, i created on Service Purchase Order in ME21N and listed the activities performed.
1) I need to make an advance payment of 10%. How do i make an entry in SES to allow accounts make the advance payment?
2) Sometimes, there will be partial payments. And after the project is completed, there may be late penalty for example 5%. But after doing SES for the partial payments, i am not able to modify the PO pricing conditions since it has already done SES. How do i go about this problem?
Appreciate if anyone could help.
Thanks

Hi,
you can save invoices before GR documents when you set up your system according to the information from knowledge base article 1496165.
Regarding subcontracting in service PO item, please refer to note note 634395, question 1.
Regards,
Edit

Good receipt 101 against subcontracting PO with 543 O madatory / compulsory

Hello,
When i do the good receipt against the subcontracting PO (MIGO). I want that the consumption of the subcontracting stock should be compulsory.
Actually in migo if i remove the ok tick from the 543 O mvt type line item then only the 101 happens with any consumption of the vendor stock material which was send for sub-contracting.
Please tell is there any way that the goods reciept for subcontract PO is only possible if and only if i am doing consumption of the material with movement type 543 O.

Hi Atul,
As per my best knowledge it is not possible to set.
Users can modify it but please consider that sometimes the components consumption may deiffer from the rate defined in the BOM (and thus in the PO component list).
So, sometimes users need to modify it or even remove the flag from that row.
Please read this link:
Re: Subcontracting Item Consumption of material issue
BR
Csaba

Special Procurement using External Procurement & Subcontracting

Hello everyone!
We currently have a material that is set up as "F" Procurement Type (External) with Special Procurement Type "30" (Subcontracting). We have active scheduling agreements for subcontracting procurement of this material. User also needs to be able to create scheduling agreements for this material where the special procurement type will be "20" (External) to be able to purchase directly from a different vendor.
We know that we can only assign one special procurement method (i.e. subcontract (L)) to a special procurement type for MRP. Therefore, my challenge to all of you is to help me find a way to procure as an external part . Is there a process which will allow this?
I am trying to create new sched. agreements but the system is validating the procurement type we settled for the material as type 30. We know that we can modify the message to a "w" type, but actually i there any problem expect if we doing it? It is that all that we have to do?
Any help will be appreciate it .

In this case, you should look at only keeping Procurement type as "F" and Special procurement key as "blank" which give you the flexibility to do both, subcontracting as well as direct procurement.
Also is your MRP run resulting in schedule lines being created in the scheduling agreement?

Subcontracting PPMs for two subcontractors

Hi all,
We have an issue using subcontracting in SNP.
The demand from the customer is to have two subcontracting options available for a material/locations, and the planning to be split by a quota.
In ECC we have in the material master a prod. version (X001), using a dummy subcontracting work-center.
Also we have two info-records, both having the production version (X001) attached.
In APO 4.1 we have two external procurement relationships (as expected from two PIRs) and two PP/DS PPMs (for both subcontractors).
But both PP/DS PPMs have the same Plan name, they differ only by the source of supply. And as the mode generation combination is created by the PP/DS Plan name, it creates only one, therefore we get only one SNP PPM - using one (the older) of the subcontractors. If a planned order is created in the second one, the order has no source of supply.
What is wrong in our scenario? Is there a way to use two subcontractors at the same time (for the moment the only problem seems to be the missing SNP PPMs)

Does your vendor's supply more than 1 plant? If so, you should use location type subcontractor vs vendor.
You will need to modify the naming convention for SNP PPM's.
Most of the clients I have been at, modified the naming convention for both PP/DS and SNP PPM's to match a more simplified and logical naming convention.
Ken Snyder

MM subcontracting Account determination

Hi All,
Any one knows MM subcontracting Account determination in OBYC?
any help is appreciated..
Thanks,
Rau

Hi,
Hi,
For Account Determination 5 major characteru2019s are as follow:
1.Chart of Account,
2.Valuation Class,
3.Transaction Event Key,
4.Valuation Grouping Code,
5.Account Grouping Code/Account Modifier.
Configuration of Automatic Account Determination with T.Code are as follow:
1.OMSK: valuation Class with Account category reference,
2.OMWM: Active Valuation Grouping Code,
3.OMWN: Active Movement type with G/L account,
4.OMWD: Active Valuation Area,
5.OMWB: Active Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
In OMWB or OBYC
Click TE key and enter Chart of account and then save the Roles 1st for
1.Debit/Credit
2.General modification
3.Valuation Modif
4.Vakuation class
And then enter respective critetia for that TE key and save.
If assignment(Chart of account,Valuation Grouping Code,Account Grouping Code,Valuation Class and G/L acocounts
are correct and u would not face any problems in G/GI/IV.
The TE keys are:
Expense/revenue from consumption of consignment material (AKO)
This transaction is used in Inventory Management in the case of
withdrawals from consignment stock or when consignment stock is
transferred to own stock if the material is subject to standard
price control and the consignment price differs from the standard
price.
u2022 Expenditure/income from transfer posting (AUM)
This transaction is used for transfer postings from one material to
another if the complete value of the issuing material cannot be
posted to the value of the receiving material. This applies both to
materials with standard price control and to materials with moving
average price control. Price differences can arise for materials
with moving average price if stock levels are negative and the stock
value becomes unrealistic as a result of the posting. Transaction
AUM can be used irrespective of whether the transfer posting
involves a transfer between plants. The expenditure/income is added
to the receiving material.
u2022 Provisions for subsequent (end-of-period rebate) settlement (BO1)
If you use the "subsequent settlement" function with regard to
conditions (e.g. for period-end volume-based rebates), provisions
for accrued income are set up when goods receipts are recorded
against purchase orders if this is defined for the condition type.
u2022 Income from subsequent settlement (BO2)
The rebate income generated in the course of "subsequent settlement"
(end-of-period rebate settlement) is posted via this transaction.
u2022 Income from subsequent settlement after actual settlement (BO3)
If a goods receipt occurs after settlement accounting has been
effected for a rebate arrangement, no further provisions for accrued
rebate income can be managed by the "subsequent settlement"
facility. No postings should be made to the account normally used
for such provisions. As an alternative, you can use this transaction
to post provisions for accrued rebate income to a separate account
in cases such as the one described.
u2022 Change in stock (BSV)
Changes in stocks are posted in Inventory Management at the time
goods receipts are recorded or subsequent adjustments made with
regard to subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
Stock posting (BSX)
This transaction is used for all postings to stock accounts. Such
postings are effected, for example:
In inventory management in the case of goods receipts to own
stock and goods issues from own stock
In invoice verification, if price differences occur in
connection with incoming invoices for materials valuated at
moving average price and there is adequate stock coverage
In order settlement, if the order is assigned to a material with
moving average price and the actual costs at the time of
settlement vary from the actual costs at the time of goods
receipt
Because this transaction is dependent on the valuation class, it is
possible to manage materials with different valuation classes in
separate stock accounts.
Caution :
Take care to ensure that:
A stock account is not used for any transaction other than BSX
Postings are not made to the account manually
The account is not changed in the productive system before all
stock has been booked out of it
Otherwise differences would arise between the total stock value of
the material master records and the balance on the stock account.
Revaluation of "other" consumptions (COC)
This transaction/event key is only relevant to Brazil. It is used if
a revaluation report is used for company codes in Brazil.
The revaluation report uses the actual prices determined by the
material ledger/actual costing to:
Revaluate costs on the basis of actual prices
Post the price differences arising from "other" consumptions
(e.g. consumption to cost center) to a collective account
This transaction/event key is needed to post the price differences.
The account specified here is posted with the price differences for
"other" consumptions.
o documentation currently available.
Small differences, Materials Management (DIF)
This transaction is used in Invoice Verification if you define a
tolerance for minor differences and the balance of an invoice does
not exceed the tolerance.
Purchase account(EIN), purchase offsetting account (EKG), freight
purchase account (FRE)
These transactions are used only if Purchase Account Management is
active in the company code.
Freight clearing (FR1), provision for freight charges (FR2), customs
duty clearing (FR3), provision for customs duty (FR4)
These transactions are used to post delivery costs (incidental
procurement costs) in the case of goods receipts against purchase
orders and incoming invoices. Which transaction is used for which
delivery costs depends on the condition types defined in the
purchase order.
You can also enter your own transactions for delivery costs in
condition types.
External service (FRL)
The transaction is used for goods and invoice receipts in connection
with subcontract orders.
If the account assigned here is defined as a cost element, you must
specify a preliminary account assignment for the account in the
table of automatic account assignment specification (Customizing for
Controlling) in order to be able to post goods receipts against
subcontract orders. In the standard system, cost center SC-1 is
defined for this purpose.
External service, delivery costs (FRN)
This transaction is used for delivery costs (incidental costs of
procurement) in connection with subcontract orders.
If the account assigned here is defined as a cost element, you must
Offsetting entry for stock posting (GBB)
Offsetting entries for stock postings are used in Inventory
Management. They are dependent on the account grouping to which each
movement type is assigned. The following account groupings are
defined in the standard system:
AUA: for order settlement
AUF: for goods receipts for orders (without account
assignment)
and for order settlement if AUA is not maintained
AUI: Subsequent adjustment of actual price from cost center
directly
to material (with account assignment)
BSA: for initial entry of stock balances
INV: for expenditure/income from inventory differences
VAX: for goods issues for sales orders without
account assignment object (the account is not a cost
element)
VAY: for goods issues for sales orders with
account assignment object (account is a cost element)
VBO: for consumption from stock of material provided to
vendor
VBR: for internal goods issues (for example, for cost
center)
VKA: for sales order account assignment
(for example, for individual purchase order)
VKP: for project account assignment (for example, for
individual PO)
VNG: for scrapping/destruction
VQP: for sample withdrawals without account assignment
VQY: for sample withdrawals with account assignment
ZOB: for goods receipts without purchase orders (mvt type
501)
ZOF: for goods receipts without production orders
(mvt types 521 and 531)
You can also define your own account groupings. If you intend to
post goods issues for cost centers (mvt type 201) and goods issues
for orders (mvt type 261) to separate consumption accounts, you can
assign the account grouping ZZZ to movement type 201 and account
grouping YYY to movement type 261.
Caution
If you use goods receipts without a purchase order in your system
(movement type 501), you have to check to which accounts the account
groupings are assigned ZOB
If you expect invoices for the goods receipts, and these invoices
can only be posted in Accounting, you can enter a clearing account
(similar to a GR/IR clearing account though without open item
management), which is cleared in Accounting when you post the vendor
invoice.
Note that the goods movement is valuated with the valuation price of
the material if no external amount has been entered.
As no account assignment has been entered in the standard system,
the assigned account is not defined as a cost element. If you assign
a cost element, you have to enter an account assignment via the
field selection or maintain an automatic account assignment for the
cost element.
Purchase order with account assignment (KBS)
You cannot assign this transaction/event key to an account. It means
that the account assignment is adopted from the purchase order and
is used for the purpose of determining the posting keys for the
goods receipt.
Exchange rate differences in the case of open items (KDM)
Exchange rate differences in the case of open items arise when an
invoice relating to a purchase order is posted with a different
exchange rate to that of the goods receipt and the material cannot
be debited or credited due to standard price control or stock
undercoverage/shortage.
Differences due to exchange rate rounding, Materials Management
(KDR)
An exchange rate rounding difference can arise in the case of an
invoice made out in a foreign currency. If a difference arises when
the posting lines are translated into local currency (as a result of
rounding), the system automatically generates a posting line for
this rounding difference.
Consignment liabilities (KON)
Consignment liabilities arise in the case of withdrawals from
consignment stock or from a pipeline or when consignment stock is
transferred to own stock.
Depending on the settings for the posting rules for the
transaction/event key KON, it is possible to work with or without
account modification. If you work with account modification, the
following modifications are available in the standard system:
None for consignment liabilities
PIP for pipeline liabilities
Offsetting entry for price differences in cost object hierarchies
(KTR)
The contra entry for price difference postings (transaction PRK)
arising through settlement via material account determination is
carried out with transaction KTR.
Price differences (PRD)
Price differences arise for materials valuated at standard price in
the case of all movements and invoices with a value that differs
from the standard price. Examples: goods receipts against purchase
orders (if the PO price differs from the standard pricedardpreis),
goods issues in respect of which an external amount is entered,
invoices (if the invoice price differs from the PO price and the
standard price).
Price differences can also arise in the case of materials with
moving average price if there is not enough stock to cover the
invoiced quantity. In the case of goods movements in the negative
range, the moving average price is not changed. Instead, any price
differences arising are posted to a price difference account.
Depending on the settings for the posting rules for
transaction/event key PRD, it is possible to work with or without
account modification. If you use account modification, the following
modifications are available in the standard system:
None for goods and invoice receipts against purchase orders
PRF for goods receipts against production orders and
order settlement
PRA for goods issues and other movements
PRU for transfer postings (price differences in the case
of external amounts)
Provision for delivery costs (RUE)
Provisions are created for accrued delivery costs if a condition
type for provisions is entered in the purchase order. They must be
cleared manually at the time of invoice verification.
Taxes in case of transfer posting GI/GR (TXO)
This transaction/event key is only relevant to Brazil (nota fiscal).
Revenue/expense from revaluation (UMB)
This transaction/event key is used both in Inventory Management and
in Invoice Verification if the standard price of a material has been
changed and a movement or an invoice is posted to the previous
period (at the previous price).
Unplanned delivery costs (UPF)
Unplanned delivery costs are delivery costs (incidental procurement
costs) that were not planned in a purchase order (e.g. freight,
customs duty). In the SAP posting transaction in Logistics Invoice
Verification, instead of distributing these unplanned delivery costs
among all invoice items as hitherto, you have the option of posting
them to a special account. A separate tax code can be used for this
account.
Input tax, Purchasing (VST)
Transaction/event key for tax account determination within the
"subsequent settlement" facility for debit-side settlement types.
The key is needed in the settlement schema for tax conditions.
Goods issue, revaluation (inflation) (WGI)
This transaction/event key is used if already-posted goods issues
have to be revaluated following the determination of a new market
price within the framework of inflation handling.
Goods receipt, revaluation (inflation) (WGR)
This transaction/event key is used if already-effected transfer
postings have to be revaluated following the determination of a new
market price within the framework of inflation handling. This
transaction is used for the receiving plant, whereas transaction WGI
(goods receipt, revaluation (inflation)) is used for the plant at
which the goods are issued.
GR/IR clearing (WRX)
Postings to the GR/IR clearing account occur in the case of goods
and invoice receipts against purchase orders. For more on the GR/IR
clearing account, refer to the SAP Library (documentation MM
Material Valuation).
Caution
You must set the Balances in local currency only indicator for the
GR/IR clearing account to enable the open items to be cleared. For
more on this topic, see the field documentation.
Thanks,
Raja

Subcontracting return delivery

Hi,
how can I post a mvt 161 for subcontracting ?
I posted a mvt 101 for the finished product which has a bill of material with two spare parts, now I'm trying to modify the purchase order and add a flag on Returns item field but the message error is:
Returns not possible for subcontracting items
How can I post the return delivery to subcontracting vendor for the finished products ?
Regards

Hi,
Think in diff . way.
why don't use '122' mvt type , and then modify your PO & again reissue the components..
The usage of 'Returnble PO' cann't be used here.
Regards
R

Subcontracting modified

Similar Messages

Maybe you are looking for