MRRL for Subcontracting vendors

Hi folks,
A batch job was being run for MRRL. For some reason, it has stopped generating the invoices for a few scheduling agreements.
Scenario:- two scheduling agreements(different materials) created referring to the same contract.
Till now, the invoices were being generated for both the agreements. Now for one it has stopped generating invoices and for other its still generating.
Where should I be looking at given that both the SA appear identical? So why would it stop generating invoices for only one?
Also, fyi.. error logs had displayed the message
SG 105
Enter rate .... rate type... for (date)..in the system settings.
As the set up is same for both, don't think this may matter. so its just an fyi..
Regards,

I've never seen this error before so cannot tell you the problem.   Since no one has replied, I'll give you some ideas on how to troubleshoot the issue.
To begin with obviously something changed - you say that the SAs are identical so start looking at other items such as the supplier, material - you have to keep digging until you find what has changed.
Secondly have you tried to create the invoice manually for the one that does not work?   Often the error will appear there as well and it is easier to identify the error when it happens using the manual process.
Good luck
Sandra

Similar Messages

Sending material for subcontract vendor two times

Hi,
I have a requirement, we create the subcontract PO as per BOM 10 different types of raw materials are required now initilaly at the time of MB1B only 8 items are ther in the system so we do the trasnfer posting for 8 items then subcontract challan create ref. to MB1B document number now later we recd the remaining two items in our system now how to issue that two material aganist the challan.
regards,
zafar

Hi All,
   Thanks for your reply, I per above reply I try one in development server,
Subcontract Po created for one FG material Qty : 1, the Finish good BOM contain 2 raw materials
Finish Material : FG1
BOM Comp.     : RM1
BOM Comp.     : RM2,
when I have done the transfer posting posting first time I have transfer only RM1 to vendor with 541 movement type, then ref. to that document number I have created Subcontract challan with J1IF01 so as per Transfer posting doc. in challan only RM1 come, then without transfering the the RM2 when I am making GR for FG material system is posting both RM1 and RM2 to consumption even for this challan i have not transfer the RM2 to vendor, so withotu saving the GR then I have trabsfer the RM2 to vendor against the same PO with MB1B movt. 541 now both the RM1 and RM2 are transfer to vendor but with different document now when I made the GR both the RM1 and RM2 are posted to conusmption but when I ma doing reconcilliation for the challan and GR system is giVING ERROR MESSAGE
Material 229 is not assigned fully, short by 1.000 NO
Message no. 8I574
as this material I have transfer in secodn document and this is not there in the challlan so is there any other method so this.
regards,
zafar

Project stock material for subcontracting

Hi,
I want to send project stock material (special stock with 'Q') for subcontracting vendor. Pl elaborate the procedure.
Subcontracting PO is with account assignment category 'Q'.
Pl revert.

Hello Sachin
We had similar requirement but in a different way. i.e sending material for subcontracting work for materials returned by customers getting it reworked bringing the reworked material back to plant stock and then sending to customer.
We had used alltogether different transactions ADSUBCON is the transaction code. Prerequsite is you will have to implement BADI BADI_ADSUB_MVT_TYPES of enhancement specefe ES_BADI_ADSUB_MVT_TYPES.
Regards

How to explode Vendor wise BOM in PO for subcontracting?

Hi,
In subcontracting process we issue cloth to subcontractor for stiching the trouser. There are two vendors for this. One require 115cm of cloth and other vendor needs 120cm of cloth. We have created two BOM, one alternate BOM for 115cm and another alternate BOM for 120cms.
The issue is when I create PO, same BOM is getting exploded for both the vendors. Whereas I want vendorwise BOM to get exploded in PO while creating the PO with relevent vendor ( For first vendor 120 cm and for second vendor 115cm).
How the relevent BOM can be picked in PO?
Thanks,
Satish

Thanks Veer,
I have tried to do as you have suggested, but it gives the error as Production Version 3 for the material xxxxxx and plant yyyy does not exist. Where do I maintain this?
Satish

Error : T161W: Vendor+subcontracting vendor not allowed for 2-step stock tr

Hi Gurus,
When we creating a STO to sub contractor vendor ( in the delivery address tab we are entering the vendor # and activating the SC vendor check box)we are getting the error message as "T161W: Vendor+subcontracting vendor not allowed for 2-step stock transfer".
Message no: MEPO140
Note:
The STO is creating with out error in ECC 5.0 for the above scenario but when i'm trying the same in ECC 6.0 in another system I'm getting this error, Can any one please advice.
Thanks in advance,
Sai

Hi Charlie
I had same issue and we sloved it. but i have one more issue here.
We have created Po and SC Vendor is not check marked. When we go into the change mode of Po i can't see the field at all. but its availalbe in disply mode.
I am using ECC 6.0, Please suggest why this is happening. I need to put check mark for SC vendor.
thanks,
Raju

Subcontracting Info record for Same Vendor which is used in Purchasing vendor

Hi Gurus,
When we want to create info record for both standard and sub contract with one single vendor., system is not creating a separate info record.
It is considering the same Info record for all the options. This triggers error - Info record price does not match.
Reg,
Suresh

Yes.. That's correct. System will just update the same info record number.. But you should not face any problem for price fetching...
System will work properly for standard PO and subcontracting PO..
System will compare the item category of info record and PO line item, as per this comparison, system will pick the price from info record..
You can see in the above screen shot the value 3 indicates that it is for subcontracting PO.
Standard PO :
I am just changing the item category from blank to L.
Subcontracting PO:
**Edited by: Dëv Päträ

Vendor field on PO for Subcontracting

Their is a vendor field (EMLIF) and subcontracting vendor field (LBLKZ) that can be used with subcontracting PO's. Is there a way to default this from the PO info record? I have searched thru this forum and other locations. The only thing I have seen is you might be able to default this from a contract.
I would appreciate any ideas on defaulting these 2 fields besides using contracts.
Thanks,
Mark

Hi,
Only way this can be done would be through enhancement, rather than defaulting the field from Info Record (especially subcontractor vendor field) maintain Z table and populated them from there based on (say document type, item category) etc.
Hope you find this useful.
Reetesh
Edited by: Reetesh on Nov 19, 2011 9:35 PM

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

PO number and material issued against this PO for subcontracting

How to know the link in between the PO number and material issued against this PO for subcontracting.
I have checked that PO history is not getting updated.
Thanks,

Hi,
We have 2 different scenarios where you can post a goods issue to Subcontract Venodrs.
Scenarios 1: You can post the goods issue against a subcontrac vendor with out referencing the Subcon PO from ME2O, at this stage we will be knowing what is the stock at subcontract vendor but we will not be knowing the issues against which and how much Quantities are posted.
So when we are post goods receipt, then we will come to know the consuption quantities.
Scenario: 2, If we use the delivery concept then we can track the goods issues against the subcon POs.
If you really keen to track the material issued to Subcon vendor against a PO so better use with delivery.
Thansk,
Satya.

Sale Order Subcontracting & Vendor wise stock

Dear Gurus,
I have one doubt we are doing sale order subcontracting transfer posting by 311 E to vendor. so is it really need to create vendor wise storage locations to track the stock at vendor end, as we have no. of vendors for subcontracting and storage location is part of organization structure.
so is it advisable to go like that ? or please suggest me any other way to track the stock at vendor end sale order wise.
Thanks & regards,
Akshay

Hello Sir ,
As it is not possible to send material which are already in special stock (sale order stock ) to subcontractor by 541 movement type , it is recommended to transfer by 311 E my MB1B or MIGO...
while doing good receipt 101 E and 543 E will going to happen , for 543 E system will automatically ask storage location. i have done already this but there only one subcontractor was there,
and in this client we have more than 80 subcontractor so i am hesitating to do this....
Subcontracting for Sales Order Stock and Project Stock - Managing Special Stocks (MM-IM) - SAP Library
Sale Order Subcontracting & Vendor wise stock

Problem for Goods Receipt for Subcontracting Purchase Order

Dear all,
Presently, we are using SAP version 4.6C and we need to introduce GR for
Subcontracting Purchase Order. We have developed a ABAP program to handle
subcon Goods Receipt by uploading flat-files from our subcontractor. The
scenario is as follows :
Goods Receipt for Subcontracting Purchase Order
1. In the ABAP program, function BAPI_GOODSMVT_CREATE will be used for goods
movement.
2. Data provided to the function are as follows :
- Posting date
- Document date
- Material number
- Plant
- Storage location
- Batch
- Movement type (101)
- Quantity
- Purchase order number
- Purchase order item
- Movement indicator (B - Goods receipt for purchase order)
3. The function will do data verification and automatically determine GI
item for subcon stock:
- Movement type (543)
- Special stock (O - parts prov. vendor)
- Material
- Quantity
- Plant
Our problem is that :
Only the GR item in the interface is to be transferred and the GI item is
determined by the system. So, the quantity for subcon stock cannot be
changed using this BAPI. Then the system will continue processing the goods
receipt and create material document.
Manually, by using transaction code MIGO, the user can display the subcon
stock data and then change the quantity.
By using transaction code MB01, after the user fills in all the GR fields,
the system comes to line item 002 (subcon stock data) and then quantity can
be changed.
As per user requirement, quantity for GI item must be same with the quantity
that has been transferred to subcon vendor in Delivery for Subcon
(transaction code VL02N).
We cannot achieve this requirement by using the BAPI mentioned above. Would
appreciate any valuable help from anyone who is able to help us on this
matter. Are there any other BAPI's that can help us to achieve the same
result ?
Thank you in advance and best regards.

As far as i understood the problem I suggest u to create the
BDC according to user actions that are performed in he manual
operation.
I can't say that the BAPI performs the exac solution what you want.
I have done some BDC work using MB01 and suggest you to be careful
and try to keep the complete in the logic as some chages in rows in BDC will
change the complete scenario.And throw correct quantity val in correct
material
row.
This methodology will help u even in mass uploads.
Or in case of automation u can perform the call transaction BDC in
background mode.
so As per my understanding bdc program is the solution. pls try and let me
know.

Batch number issue when posting goods receipt for Subcontracting PO

Dear expert,
I always heard there will be issues while posting goods receipt for subcontracting PO. If the component is managered by batch.
No batch number will be proposed during PGR in MIGO...
I dont quite understand where is the issue??
My understanding:
We have batch managered components and End Product. All have batch numbers, then we PGI the stock to 'SC stock' via 541 movement type.
Then Vendor will finish the end product and send us back the end product.
We consumption the components use 543 O movement type? And GR the end product..
So while goods receipt, the sytem just need pick the existing batch number for both components and finish products..
Where are the issues???
Thanks.

Hoo Laa wrote:
I have questions for people always mentioning there are issues with batch determination while post goods receipt for subcontracting orders.
>
> I am thinking maybe they didnt active the batch determination for 543 movement type..
>
> Thanks.
Hi Hoo,
You are right!!
Setting of batch number determination has its importance in Mvt Type be it 541, 543....
The issue you might have observed would be with Batch Determination in Goods Issues which folks find it bit tough to achieve n make it work for them.
Cheers!!
Shiva

Automatic Batch Determination for Subcontracting Process(ME2ON)

Dear All,
When we are issuing the components to subcontracting vendor in ME2ON t-code, system is not picking the batch automatically like while creating delivery. In Sales for automatic batch determination they are using item category group but for subcon. order we have only delivery type.
Is SAP will support automatic Batch determination while issue the goods through ME2ON?
If yes kindly revert back.
Thanks &Regards,
Edited by: Priya on Nov 7, 2011 11:40 AM

Hi,
Go to SPRO > Logistics - General > Batch Management > Batch Determination and Batch Check > Batch Search Procedure Allocation and Check Activation > Allocate IM Search Procedure/Activate Check > Here assign Batch Search Procedure "ME0001" to Movement Type 543 O
Then go to MBC1 and maintain condition record for Strategy Type ME02 i.e. Plant and here keep selection method as "O"
In MIGO, click on "Stock Determination" button for automatic batch determination.

Clearing of Change in Stock Account at the time of GR for Subcontracting

Dear,
We have created a PO with Item Category "L" for subcontracting.
At the time or GR system has posted below accounting entries:
GR/IR clearing account 500 -
External service account 500 +
Stock account: end product 950 +
Change involving stocks 950 -
Stock account: comp. 450 - (components cost)
Consumption account 450 +
I want to know how to clear Change in Stock Account.
Please advise.
Regards,
Vivek

Hi:
        As per my understanding this happens when MIGO is done in case of a subcontracting PO
Stock-CS/RM                                     Dr
GR/IR Clear RM/PM/CS                             Cr
Inventory Change Sub-Cont RM     Dr
Ext Serv Sub-Cont                             Dr
Stock-CS/RM                                             Cr
Sub-Cont Cons RM                             Dr
Upon MIRO
Ext Serv Sub-Cont                             Cr
GR/IR Clear RM/PM/CS             Dr
Inv Change Sub-Cont RM     Dr
Vendor                                            Cr
Duties                                      Dr
Stock-CS/RM                                   Cr
Hence Inventory change account is cleared as soon as MIRO is done. Hope it will clear your understadning
Regards

Excise details for IMPORT vendor

Hi SAP ients
While Doing J1IEX_P for import vendor system gives error msg "maintain Excise details for the vendor"
But for IMPORT vendor we dont maitain such details
Am I right?
Can anybody help?
santosh j

Thanks Pankaj
It is working
I have another question Regarding Subcontracting
When we send the material to supplier it is done thr' 4(5) (a) excise challan whose limit is 180 days (material should come back to parent company within 180 days)
But now Excise has issued new amendment / form ie 4(5)(b) for sending the CAPITAL GOODS ie dies/ moulds etc for the production purpose at supplier's end against form 4(5)(b) instead of 4(5) (a) whose validity is @ 2 years or more
Is there any standard format in SAP for that? OR
Any new note released by SAP?
Thanks in advance
Santosh Jagtap

MRRL for Subcontracting vendors

Similar Messages

Maybe you are looking for