QM Procee for bello scnerio

HI QM Experts,
I am a PP consultant and want to map following scnerio
1 Quality at the time of  Goods issue(GI)  also i can skip that if i want
2 Quality at the Time of GR , Also i can skip that when i want
3 . Quality certifacate at the time of delivery
Please explain in detail with master data , IF there are PPT of QM Pls send me at- k ge erish @ g mail.co m   that will be a grate help
Thanks in advance
Regards
Girish

All of your scenario are covered by SAP standard process.
1. Implement goods issue inspection and use dynamic modifiction for contorl 'skip' lot.
2. Implement goods receipt inspection and same.
3. Implement quality certificate for outbound delivery.
You can try to study it though SAP help portal.
Regards
Luke

Similar Messages

  • Procees for upload field in mkpf&mseg table

    Hi friends,
    i had return the code for uploading two fields in mkpf and mseg table  .when i am executing through f8 the updated value is not founding when we checkd through debugging the value is updating and appering in screen plz tell me how i will solve the issue.
    for u r referenece i am sending the code what i had return in logic.
    types: BEGIN OF it_tab,
            prueflos(16) type c,
            MBLNR type mblnr,
            TYP type QAMBTYPE,
            END OF it_tab.
          types: begin of it_tab1.
           include type mkpf.
          types: END OF it_tab1.
          types:begin of it_mseg.
          include type mseg.
          types:end of it_mseg.
    *        end of it_tab1.
         types: ts_tab1 type STANDARD TABLE OF it_tab1.
         types: ts_mseg type STANDARD TABLE OF it_mseg.
         data: ts_tab type STANDARD TABLE OF it_tab,
               wa_tab type it_tab,
               wa_tab1 type it_tab1,
               ts_tab2 type ts_tab1,
               ts_mseg type ts_mseg,
               wa_mseg type it_mseg,
               it_tab12 type  it_tab1 OCCURS 0 WITH HEADER LINE.
           select PRUEFLOS mblnr typ from QAMB
             into table ts_tab  where prueflos = it_final-prueflos
                                  and    typ = '3'.
             if ts_tab[] is not INITIAL.
               sort ts_tab[] by mblnr.
              select * from mkpf into TABLE ts_tab2 FOR ALL ENTRIES IN ts_tab where mblnr =  ts_tab-mblnr.
                if ts_tab2[] is not INITIAL.
                  sort ts_tab2[] by mblnr.
                  select * from mseg into table ts_mseg FOR ALL ENTRIES IN ts_tab2 where mblnr = ts_tab2-mblnr.
                    endif.
                endif.
             loop at ts_tab into wa_tab .
               READ TABLE ts_tab2 into wa_tab1 with key mblnr = wa_tab-mblnr.
               wa_tab1-FRBNR = it_data1-FRBNR.
               if sy-subrc eq 0.
                wait UP TO 2 SECONDS.
              update mkpf from wa_tab1.
              COMMIT WORK .
               endif.
               read table ts_mseg into wa_mseg with key mblnr = wa_tab1-mblnr.
               wa_mseg-sgtxt = it_data1-trucknum.
               if sy-subrc eq 0.
                 wait UP TO 2 seconds.
              update mseg from wa_mseg.
              COMMIT WORK .
               endif.
               ENDLOOP.
    thanks in advance,
    siva
    Edited by: Thomas Zloch on May 13, 2011 1:37 PM - please use code tags

    it is added in bdc code  only.
    now i will explaing proccess of bdc . this is used for converting meterial type from 103 movement type to 105 move ment type so whaterver data they got through 103 movemet type (migo data) they are uploading through xl and uploading through our bdc
    after uploading they are used QA11 tcode .record is done for this after recording completed it is converting 103 to 105 move ment type  and it is displaying message like succesfully proceesed . inthis 105 movement type we are not getting bill of lading no and truck no so i am updating these two field in this table so i done like this so do u get any idea to update the fields in another way means plz help me
    siva.

  • Returns procees for 3rd party

    Hi Guru's
    Please let me know what is the Return process for 3rd party order
    Thanks in advance
    Mastan

    Dear Mastan,
    quite generally, you can book the reurned goods as you want (to your vendor or to your company). There is no standard process from SAP side here.
    Concerning creation of invoice, it depends on your Customizing setting for the item category (transaction VOV7). If the billing relevance is 'F' (recommended for the third-party), then you cannot create the invoice without incoming invoice. If you have another billing relevance (for example , 'B' according to order quantity), then you can create invoice without incoming invoice. Moreover, in case of 'B' you can create the invoice immediately after creation of the order. It is independent on return.
    As I have already said, there are no standard rules for this process at SAP. And the whole process is not supported at all. Therefore you have always to decide by yourself, what would be reasonable for your business. There are no guidelines from SAP side here.
    I hope, this info helps you a little bit further.
    Kind regards,
    Akmal Vakhidov
    Development Support SD, SAP, Walldorf/Germany

  • Process flow for the Mid-year Status Changes based upon the Qualifying Even

    Hi Experts,
    I'm looking some information for the process flow for the Mid-year Status Changes based upon the Qualifying Events. Basically, I need to know, what would be the impact of these changes on various info types (Via IT0014 - Deduction changes & so forth) and the things that needs to be considered during it's Configuration and the things that needs to be checked due to the occurrence of the change. I would greatly appreciate any kind of help/document.
    Thanks a bunch in advance,
    Thanks,
    Exertive.

    Hello guys,
    Can anyone has any kind of input on this? Basically, I need to know the procees for Mid-year status changes based upon Qualified events. Any kind of help is greatly appreciated.
    Thanks,
    Exertive.

  • MRP lot sizing proced.(OMI4) Std config. u00A0

    Hi friendz,                                   
    What is the config for MRP lot sizing proced. for following scenarios.                                   
    Period lot size according . to plng calendar     
    Period Lot size;plng calendar;end rec                                   
    Period lot size according. to plng cal.for PP               
    Replenish to maximum stock level                                   
    Repl to max stock level w/requirements                                   
    Thanks and regards,                                   
    Solomon

    hi,
    suppose i m mantaining the lot size PA, Lot size proc. -P,  lot size indi - K, and no of periods - 1,
    now the same way if i want to maintain lot size PP - (Period lot size acc. to plng cal.for PP) wt are the other fields in OMI4 i have to maintain.
    hope u can understand the above scenario.
    Thanks,
    Solomon

  • Pricing procedure error in Sales Order

    Hi,
    I have made all necessary SD config. setting for pricing procedure creation and determination in Sales orders. But while creating a sales order I am getting an error as "No pricing procedure could be determined as entries are missing in TAble 683v. but I can see the relevant entry in this table. How this error can be rectified. i am unable to procees for sales order creation.

    Hi,
    Check in sales document type - VOV8 Which document price procedure you maintained under transaction flow tab
    Check in customer master which customer master pricing procedure maintained in sales area data >> sales tab >> pricing/statistic.
    Then in pricing procedure determination OVKK maintain
    Sales orgz + Dchl + Div + Document price procedure + Customer price procedure = PRICED PROCEDURE
    Kapil

  • Third-party not defined in the case of vendor with plant assignment ?

    We use a Third-Party Vendor to direct-ship some products directly to our Customers.
    When transfers third party order form's PR STO PO, prompts the following information
    Third-party not defined in the case of vendor with plant assignment
    Message no. 06769
    Diagnosis
    You are entering a purchase transaction involving a vendor to whom a plant has been assigned. Normally, this will involve the transfer of materials from one plant to another.
    This process necessitates a delivery and a billing document in the SD system. The PO appears directly in the delivery due list of the issuing plant (vendor) and therefore does not need to be transmitted.
    However, an item with the procurement form "third-party" (triangular business deal) cannot appear in the delivery due list.
    Procedure
    An item with the procurement form "third-party" can only be ordered from vendors without a plant assignment.
    how should solve?
    Many thanks,  Adny.
    Edited by: Andy Yao on Feb 8, 2010 3:58 AM

    Hi Andy
    Why u doing stock transfer order,in third party sales there is no stock transfer
    Follow below procees for third party sales( Vendor ship materials directly to customer)
    Create Sales order(Use item category TAS) >>> Purachase requisition(Automatically from order) >>> Purchase order >>> Vendor Invoice Verification >>> Invoice to customer
    Kapil

  • Vendor subrange and vendor rention level???

    Hii
    can smoebody explain me aboutt the below topics related to vendor .
    1. Vendor subrange ??
    2.Vendor rention level.??
    Explain me what are the impartance about this ...
    Thanks
    SAP-MM

    HI,
    Vendor Sub-Ranges (VSRs) subdivide a vendoru2019s total product range according to a variety of criteria.
    You can specify which materials or articles belong to which VSR in the info records of the relevant vendor. There you can also specify the sequential position of the material in the vendor sub-range, so that the items of a purchase order are sorted into the sequence in which your vendor expects them.
    In the SAP System, you can maintain certain data at vendor sub-range level. For each sub-range:
    You can maintain different data In addition to the purchasing data or partners that have been created for a purchasing organization, you can enter different data or partners in the vendor master record for each vendor sub-range, e.g. different ordering addresses, terms of payment, or partner roles.
    For Example :-
    Scnerio:
    The Vendor currency is maitained (say) USD and you want to attach EURO, GBP to the existing vendor without creating same Vendor in Data Base
    T-code XK02 u2013 Select Vendor and then Select Purchasing Data
    In Purchasing Data View go to MENU BAR -> Extras -> ADDITIONAL PURCHASING DATA 
    In the Screen Select check the box for
      1. DATA RETENTION AT VSR LEVEL ALLOWED
      2. DATA RETENTION AT PLANT LEVEL ALLOWED
    T-code XK02 u2013 Select Vendor and then Select Purchasing Data
    In the PURCHASING DATA VIEW, a Button appears in Sub-Menu Bar which Says u201CSUB-RANGEu201D
    D.  Click on it and put in the Currency Code and Currency Description
    e.g.
    USD US DOLLAR
    GBP Great Britain Pound
    INR India Rupee
    E.  SAVE
    M. T-code XK02 u2013 Select Vendor and then Select Purchasing Data
    In the PURCHASING DATA VIEW, select u201CALTERNATIVE DATAu201D
    N. A new Screen is Displayed, PRESS F5, and repeat the steps H to L
    Multiple Currencies are now Defined / attached to the Vendor.
    Hope HElp u !
    Regards,
    Pardeep Malik

  • Creating error message in enter query mode

    Thanks u3 and am0x,
    Thanks for your answer.Now i want to implement the same thing for another scnerio.
    Suppose i have entered a certain date but there is no related data in the database for .I am concedering it as a error and want to show a message.
    In the trigger ON-ERROR i have written this code.
    DECLARE
    err_code NUMBER := ERROR_CODE;
    err_type VARCHAR2(3) := ERROR_TYPE;
    msg VARCHAR2(2000) := ERROR_TEXT;
    BEGIN
    IF err_code = 40358 AND err_type = 'FRM' THEN
    message('please enter date as 01-jan-2008');
    END IF;
    IF err_code = 40301 AND err_type = 'FRM' THEN
    message('there is no related data in the database ,please enter the value again');
    END IF;
    RAISE FORM_TRIGGER_FAILURE;
    END;
    But it is not showing any message if there is no related data in the database can you please help.

    That looks like it should work, but you have left out an important line which could tell you why it's not working. If the error code is not one of the two you have specified then there will be no message at all!
    Try this and see what error message you get. Perhaps the code is something other than 40301.
    DECLARE
      err_code NUMBER := ERROR_CODE;
      err_type VARCHAR2(3) := ERROR_TYPE;
      msg VARCHAR2(2000) := ERROR_TEXT;
    BEGIN
      IF err_code = 40358 AND err_type = 'FRM' THEN
        message('please enter date as 01-jan-2008');
      ELSIF err_code = 40301 AND err_type = 'FRM' THEN
        message('there is no related data in the database ,please enter the value again');
      ELSE
        message(err_type||'-'||to_char(err_code)||': '||msg);
      END IF;
      RAISE FORM_TRIGGER_FAILURE;
    END;

  • COMM_SRTUCTURE is uknown when migrating data flow bw 3.x to 7.4

    Dear ALL,
    2LIS_13_VDHDR data flow migrating 3.x to 7.x , ABAP syntax error COMM_STRUCTURE is unknown infosoure transformation level, present we are using 7.4 sp5 . after migration ABAP code
    TYPES:
          BEGIN OF _ty_s_TG_1_full,
    *      InfoObject: 0CHNGID Change Run ID.
            CHNGID           TYPE /BI0/OICHNGID,
    *      InfoObject: 0RECORDTP Record type.
            RECORDTP           TYPE /BI0/OIRECORDTP,
    *      InfoObject: 0REQUID Request ID.
            REQUID           TYPE /BI0/OIREQUID,
    *      InfoObject: 0CALDAY Calendar Day.
            CALDAY           TYPE /BI0/OICALDAY,
    *      InfoObject: 0CALMONTH Calendar Year/Month.
            CALMONTH           TYPE /BI0/OICALMONTH,
    *      InfoObject: 0CALWEEK Calendar year / week.
            CALWEEK           TYPE /BI0/OICALWEEK,
    *      InfoObject: 0FISCPER Fiscal year / period.
            FISCPER           TYPE /BI0/OIFISCPER,
    *      InfoObject: 0FISCVARNT Fiscal year variant.
            FISCVARNT           TYPE /BI0/OIFISCVARNT,
    *      InfoObject: 0BILLTOPRTY Bill-to party.
            BILLTOPRTY           TYPE /BI0/OIBILLTOPRTY,
    *      InfoObject: 0COMP_CODE Company code.
            COMP_CODE           TYPE /BI0/OICOMP_CODE,
    *      InfoObject: 0DISTR_CHAN Distribution Channel.
            DISTR_CHAN           TYPE /BI0/OIDISTR_CHAN,
    *      InfoObject: 0DOC_CATEG Sales Document Category.
            DOC_CATEG           TYPE /BI0/OIDOC_CATEG,
    *      InfoObject: 0PLANT Plant.
            PLANT           TYPE /BI0/OIPLANT,
    *      InfoObject: 0SALESORG Sales Organization.
            SALESORG           TYPE /BI0/OISALESORG,
    *      InfoObject: 0SALES_GRP Sales group.
            SALES_GRP           TYPE /BI0/OISALES_GRP,
    *      InfoObject: 0SALES_OFF Sales Office.
            SALES_OFF           TYPE /BI0/OISALES_OFF,
    *      InfoObject: 0SHIP_TO Ship-To Party.
            SHIP_TO           TYPE /BI0/OISHIP_TO,
    *      InfoObject: 0SOLD_TO Sold-to party.
            SOLD_TO           TYPE /BI0/OISOLD_TO,
    *      InfoObject: 0VERSION Version.
            VERSION           TYPE /BI0/OIVERSION,
    *      InfoObject: 0VTYPE Value Type for Reporting.
            VTYPE           TYPE /BI0/OIVTYPE,
    *      InfoObject: 0DIVISION Division.
            DIVISION           TYPE /BI0/OIDIVISION,
    *      InfoObject: 0MATERIAL Material.
            MATERIAL           TYPE /BI0/OIMATERIAL,
    *      InfoObject: 0SHIP_POINT Shipping point.
            SHIP_POINT           TYPE /BI0/OISHIP_POINT,
    *      InfoObject: 0PAYER Payer.
            PAYER           TYPE /BI0/OIPAYER,
    *      InfoObject: 0DOC_CLASS Document category /Quotation/Order/Deliver
    *y/Invoice.
            DOC_CLASS           TYPE /BI0/OIDOC_CLASS,
    *      InfoObject: 0DEB_CRED Credit/debit posting (C/D).
            DEB_CRED           TYPE /BI0/OIDEB_CRED,
    *      InfoObject: 0SALESEMPLY Sales Representative.
            SALESEMPLY           TYPE /BI0/OISALESEMPLY,
    *      InfoObject: 0SUBTOT_1S Subtotal 1 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_1S           TYPE /BI0/OISUBTOT_1S,
    *      InfoObject: 0SUBTOT_2S Subtotal 2 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_2S           TYPE /BI0/OISUBTOT_2S,
    *      InfoObject: 0SUBTOT_3S Subtotal 3 from pricing proced.for conditi
    *on in stat. curr..
            SUBTOT_3S           TYPE /BI0/OISUBTOT_3S,
    *      InfoObject: 0SUBTOT_4S Subtotal 4 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_4S           TYPE /BI0/OISUBTOT_4S,
    *      InfoObject: 0SUBTOT_5S Subtotal 5 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_5S           TYPE /BI0/OISUBTOT_5S,
    *      InfoObject: 0SUBTOT_6S Subtotal 6 from pricing proced. for condit
    *ion in stat. curr..
            SUBTOT_6S           TYPE /BI0/OISUBTOT_6S,
    *      InfoObject: 0OPORDQTYBM Open orders quantity in base unit of meas
    *ure.
            OPORDQTYBM           TYPE /BI0/OIOPORDQTYBM,
    *      InfoObject: 0OPORDVALSC Net value of open orders in statistics cu
    *rrency.
            OPORDVALSC           TYPE /BI0/OIOPORDVALSC,
    *      InfoObject: 0QUANT_B Quantity in base units of measure.
            QUANT_B           TYPE /BI0/OIQUANT_B,
    *      InfoObject: 0DOCUMENTS No. of docs.
            DOCUMENTS           TYPE /BI0/OIDOCUMENTS,
    *      InfoObject: 0DOC_ITEMS Number of Document Items.
            DOC_ITEMS           TYPE /BI0/OIDOC_ITEMS,
    *      InfoObject: 0NET_VAL_S Net value in statistics currency.
            NET_VAL_S           TYPE /BI0/OINET_VAL_S,
    *      InfoObject: 0COST_VAL_S Cost in statistics currency.
            COST_VAL_S           TYPE /BI0/OICOST_VAL_S,
    *      InfoObject: 0GR_WT_KG Gross weight in kilograms.
            GR_WT_KG           TYPE /BI0/OIGR_WT_KG,
    *      InfoObject: 0NT_WT_KG Net weight in kilograms.
            NT_WT_KG           TYPE /BI0/OINT_WT_KG,
    *      InfoObject: 0VOLUME_CDM Volume in cubic decimeters.
            VOLUME_CDM           TYPE /BI0/OIVOLUME_CDM,
    *      InfoObject: 0HDCNT_LAST Number of Employees.
            HDCNT_LAST           TYPE /BI0/OIHDCNT_LAST,
    *      InfoObject: 0CRM_PROD Product.
            CRM_PROD           TYPE /BI0/OICRM_PROD,
    *      InfoObject: 0CP_CATEG Category.
            CP_CATEG           TYPE /BI0/OICP_CATEG,
    *      InfoObject: 0FISCYEAR Fiscal year.
            FISCYEAR           TYPE /BI0/OIFISCYEAR,
    *      InfoObject: 0BP_GRP BP: Business Partner Group (from Hierarchy).
            BP_GRP           TYPE /BI0/OIBP_GRP,
    *      InfoObject: 0STAT_CURR Statistics Currency.
            STAT_CURR           TYPE /BI0/OISTAT_CURR,
    *      InfoObject: 0BASE_UOM Base Unit of Measure.
            BASE_UOM           TYPE /BI0/OIBASE_UOM,
    *      InfoObject: 0PROD_CATEG Product Category.
            PROD_CATEG           TYPE /BI0/OIPROD_CATEG,
    *      InfoObject: 0VOLUME Volume.
            VOLUME           TYPE /BI0/OIVOLUME,
    *      InfoObject: 0VOLUMEUNIT Volume unit.
            VOLUMEUNIT           TYPE /BI0/OIVOLUMEUNIT,
    *      InfoObject: 0FISCPER3 Posting period.
            FISCPER3           TYPE /BI0/OIFISCPER3,
    *      InfoObject: 0SALES_DIST Sales District.
            SALES_DIST           TYPE /BI0/OISALES_DIST,
    *      InfoObject: 0BILL_TYPE Billing type.
            BILL_TYPE           TYPE /BI0/OIBILL_TYPE,
    *      InfoObject: 0MOVE_PLANT Receiving Plant/Issuing Plant.
            MOVE_PLANT           TYPE /BI0/OIMOVE_PLANT,
    *      InfoObject: 0SHIP_COND Shipping conditions.
            SHIP_COND           TYPE /BI0/OISHIP_COND,
    *      InfoObject: 0AB_RFBSK Status for Transfer to Accounting.
            AB_RFBSK           TYPE /BI0/OIAB_RFBSK,
    *      InfoObject: 0AB_FKSTO Indicator: Document Is Cancelled.
            AB_FKSTO           TYPE /BI0/OIAB_FKSTO,
    *      InfoObject: 0CUST_GRP5 Customer Group 5.
            CUST_GRP5           TYPE /BI0/OICUST_GRP5,
    *      InfoObject: ZCU_COND1 Constomer Condition Group 1.
            /BIC/ZCU_COND1           TYPE /BIC/OIZCU_COND1,
    *      InfoObject: ZCU_COND2 Customer Condition Group 2.
            /BIC/ZCU_COND2           TYPE /BIC/OIZCU_COND2,
    *      InfoObject: ZBATCHCD Batch Code.
            /BIC/ZBATCHCD           TYPE /BIC/OIZBATCHCD,
    *      InfoObject: 0BATCH Batch number.
            BATCH           TYPE /BI0/OIBATCH,
    *      InfoObject: ZBATCH Batch number.
            /BIC/ZBATCH           TYPE /BIC/OIZBATCH,
    *      Field: RECORD Data record number.
            RECORD           TYPE RSARECORD,
          END   OF _ty_s_TG_1_full.
    * Additional declaration for update rule interface
      DATA:
        MONITOR       type standard table of rsmonitor  WITH HEADER LINE,
        MONITOR_RECNO type standard table of rsmonitors WITH HEADER LINE,
        RECORD_NO     LIKE SY-TABIX,
        RECORD_ALL    LIKE SY-TABIX,
        SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS.
    * global definitions from update rules
    * TABLES: ...
    DATA: IN    TYPE F,
          OUT   TYPE F,
          DENOM TYPE F,
          NUMER TYPE F.
    * Def. of 'credit-documents': following doc.categ. are 'credit docs'
    *   reversal invoice (N)
    *   credit memo  (O)
    *   internal credit memo (6)
    * Credit-documents are delivered with negative sign. Sign is switched
    * to positive to provide positive key-figures in the cube.
    * The combination of characteristics DE_CRED and DOC-CLASS provides
    * a comfortable way to distinguisch e.g. positive incoming orders or
    * order returns.
    * Def. der 'Soll-Dokumente': folgende Belegtypen sind 'Soll-Belege'
    *   Storno Rechnung (N)
    *   Gutschrift (O)
    *   Interne Verrechn. Gutschr. (6)
    * Soll-Dokumente werden mit negativem Vorzeichen geliefert. Um die Kenn-
    * zahlen positiv in den Cube zu schreiben, wird das Vorzeich. gedreht
    * Die Kombination der Merkmale DEB_CRED und DOC-CLASS gibt Ihnen die
    * Möglichkeit schnell z.B. zwischen Auftrags-Eingang oder Retouren zu
    * unterscheiden.
    DATA: DEB_CRED(3) TYPE C VALUE 'NO6'.
    FORM routine_0002
      TABLES
       P_MONITOR         structure rsmonitor
      CHANGING
        RESULT         TYPE _ty_s_TG_1_full-DOCUMENTS
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
    CLEAR RESULT.
    RESULT = COMM_STRUCTURE-NO_INV.
    IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
       RESULT = RESULT * ( -1 ).
    ENDIF.
    RETURNCODE = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    ENDFORM.                    "routine_0002
    FORM routine_0003
      TABLES
       P_MONITOR         structure rsmonitor
      CHANGING
        RESULT         TYPE _ty_s_TG_1_full-DEB_CRED
        RETURNCODE     LIKE sy-subrc
        ABORT          LIKE sy-subrc
      RAISING
        cx_sy_arithmetic_error
        cx_sy_conversion_error.
    * init variables
    * fill the internal table "MONITOR", to make monitor entries
      IF COMM_STRUCTURE-DOC_CATEG CA DEB_CRED.
        RESULT = 'C'.
      ELSE.
        RESULT = 'D'.
      ENDIF.
      RETURNCODE = 0.
      p_monitor[] = MONITOR[].
      CLEAR:
        MONITOR[].
    ENDFORM.   
    Error:
    E:Field "COMM_STRUCTURE-NO_INV" is unknown. It is neither in one of the
    specified tables nor defined by a "DATA" statement. "DATA" statement.
    communication structure chaged to sours fields but no uses , please suggest how can i proceed , Thanks in Advance immediate replay
    Thanks & Regards
    Ramesh G

    Hi Gareth,
    You have two options:
    1. Transport from BW 3.1 to BI 7.0. You'll need to create a transport route between both systems. This may cause you some troubles in the future when you want to modify the objects you transported.
    2. As there are few objects, you can use XML export utility from Transport connection. There, you make an XML file with the objects you need to transport. One thing that you may take care of, in this option, is that the business content objects you are exporting need to be activated in the destination system. Another problem is that querys are not exported.
    Since it's only a cube, maybe you can create the objects manually. Look that in BI 7.0 there are several new functionalities, i don't know how transport or xml export would work.
    Hope this helps.
    Regards,
    Diego

  • Significance of FRE

    hi
    in pricing proced for a cond type FRA1 am maintaing acct key as FRE , accrual key as FR1
    when am taking GR
    accounts are updating like this for Ex
    Inventory ac Dr   BSX  110 Rs/
    GR/IR ac Cr    WRX   100 Rs/
    Frt ac Cr          FR1   10 Rs/
    here am not understanding what is the significance of FRE
    if i remove acct key as FRE also am getting same accounts when am taking GR.
    Is this mandatory in pricing schema or not.
    as per SAP help this field is required if purchase account management active only.
    Is this wright or not.
    let me take one example & explain me
    even in STD SAP in OBYC for FRE key no G/L account assigned.
    can any one explain me
    thanks
    nani

    hi
    account key :-
    The account key enables the system to post amounts to certain types of revenue account. For example, the system can post freight charges
    as we need the freight amount separately in diffrent gl acount so we needa diffrent account key.
    so we define FRE key in acct key
    accruals means :-
    With the aid of the account key, the system can post amounts to certain types of accruals accounts. For example, rebate accruals which are calculated from pricing conditions can be posted to the corresponding account for rebate accruals.
    FRE  is used only if Purchase Account Management is active in the company code
    so u have to maintain the fre key for correct accounting and also have to give gl acct in OBYC for the same
    reward if useful
    regards
    kunal
    regards
    kunal
    Edited by: kunal ingale on Jul 22, 2008 6:44 AM
    Edited by: kunal ingale on Jul 22, 2008 6:44 AM

  • TO-BE Process

    We are in process of launcing 11i. Can anybody provide us what should be standard TO-BE procees for different Mfg. Modules.
    Is there any URL is there to get detail about this.
    Thanks
    Sushil

    Sushil : can you please elaborate a little more on what you mean by 'To-be' processes for manufacturing modules.
    Thanks

  • Hello PP Guru please help to resolve this issue

    Sometimes in production the finished material gets rejected due to some quality parameters which is lacking in the material. so the client what do is they reuse this material as a raw material (by melting it)or between the process if they have some order for such size and specification. My question is my question is how to map this in to sap.
    (this is salvaging process) in sap. ?

    Dear Verma
    For mapping this senario you have to following
    1) For Melting
    when FG is rejected do the posting in Rejection storage location
    then create an order i.e. melting order with t code CO07(like Rwork order)
    assinge all FG to that orders bom
    issue all material against that order
    and maintened ur Raw material code as By product by 531 movement in BOM
    so u consume ur FG and u will get ur Raw material in stock
    2) Between the procees
    For this u Have to do the FG posting in Rejection store
    then transfer Material to material by 309 movement
    Regards
    Ssachin

  • Wm physical inventory

    Hi,
    please send a detailed information with T.codes regarding warehouse management manual physical inventory process.
    naveen

    Hi,
    T codes
    LCO1 Set Up Warehouse Co/Material Docs.
    LCO2 Set Up Warehouse Co/Transport Orders
    LL01 Warehouse Activity Monitor
    LS01 Create Warehouse Master Record
    LS01N Create Warehouse Master Record
    LS02 Change Warehouse Master Record
    LS02N Change Warehouse Master Record
    LS03 Display Warehouse Master Record
    LS03N Display Warehouse Master Record
    LS26 Warehouse stocks per material
    MB52 List of Warehouse Stocks on Hand
    OLML IMG structure Warehouse Management
    OMLN Warehouse Control Link
    OMMF Number Ranges per Warehouse
    OMMP Decentralized Warehouse Management
    OMNG Queues Warehouse Management System
    OMNH APPC Interface per Warehouse Number
    OMNI Print Program per Warehouse Number
    OMNJ Link to Warehouse Control Unit
    OMNL Warehouse Number Maint./Inventory
    EC09 Org.Object Copier: Warehouse Number
    FMFG_WAREHOUSE Warehouse Report Transaction
    J1A5 MM Warehouse stock report (Arg.)
    LI20 Clear Inventory Differences WM
    LLVS WM Menu
    LN07 Number Ranges for WM Communic.Rec.
    LP11 WM staging of crate parts
    LP11W WM Staging for Crate Parts (IAC)
    LP12 Staging release order parts (WM-PP)
    LP21 WM replenishment for fixed bins
    LP24 WM Replenishment for Random Whse
    LPIN Info: Material Stock WM-PP
    LPK1 Create Control Cycle for WM
    LPK2 Change Control Cycle for WM
    LPK3 Display Control Cycle for WM
    LS51 Create Batch Search Strategy - WM
    LS52 Change Batch Search Strategie - WM
    LS53 Display Batch Search Strategy - WM
    LX23 Stock comparison IM - WM
    LX26 Inventory in WM via cycle counting
    LX30 Overview of WM messages ext.system
    LX41 Bin Status Report WM/PP Interface
    LX42 Evaluation PP Order from WM View
    LX46 Transmission WM perform. data to HR
    MCL1 WMS: Stck Placemt.+Remov. Selection
    MCL5 WMS: Flow of Quantities Selection
    MCL9 WM: Material Plcmt/Removal:Selection
    MCLD WM: Material Flow - Selection
    MCLH WM: Movement Types - Selection
    OMCR Inventory Sampling: St.Mgmt Lvl: WM
    OMK3 Conditions: field catalog (WM)
    OMK4 CondTable: Create (Batches, WM)
    OMK5 CondTable: Change (Batches, WM)
    MCL1 WMS: Stck Placemt.+Remov. Selection
    MCL5 WMS: Flow of Quantities Selection
    MCL9 WM: Material Plcmt/Removal:Selection
    MCLD WM: Material Flow - Selection
    MCLH WM: Movement Types - Selection
    OMCR Inventory Sampling: St.Mgmt Lvl: WM
    OMK3 Conditions: field catalog (WM)
    OMK4 CondTable: Create (Batches, WM)
    OMK5 CondTable: Change (Batches, WM)
    OMK6 CondTable: Display (Batches, WM)
    OMK7 Batch WM..... (will be deleted)
    OMKR Search Types: Optimize Access WM
    OMKT Strategy Types: Batch Determin.WM
    OMKU Access: Maintain Batch Determin.WM
    OMKV Batch Determination: Proced.for WM
    OMLL WM Movement Type: Clear Invent.Diff.
    OMLR WM Interface to Inventory Management
    OMMC Printer Assignment per WM Mov.Type
    OMMO Consistency Check for MM-WM Tables
    OMMZ Spool Parameters for WM Print Ctrl
    OMN0 Control of Transaction Codes (MM-WM)
    OMNE Control of Transactions in MM-WM
    OMNZ Parameters for Activity in WM
    WM movement types
    711 Inventory differences in unrestricted-use stock (LE-WM)
    This movement is generated automatically when you post inventory differences in the Warehouse Management System.
    Possible special stock indicators:
    E, K, M, Q
    713 Inventory differences in quality inspection stock (LE-WM)
    This movement is generated automatically when you post inventory differences in the Warehouse Management System.
    Possible special stock indicators:
    E, K, M, Q
    715 Inventory differences in blocked stock returns (LE-WM)
    This movement is generated automatically when you post inventory differences in the Warehouse Management System.
    Possible special stock indicators:
    None
    717 Inventory differences in blocked stock (LE-WM)
    This movement is generated automatically when you post inventory differences in the Warehouse Management System.
    Possible special stock indicators:
    E, K, M, Q
    319 Split structured material into components (Retail)
    You can enter the splitting of a structured material manually using movement type 319.
    You can configure Customizing so that a structured material (for example, asset, prepack, or display is automatically split into its components at goods receipt. The system posts the split using movement type 319. In this process, the BOM header material is posted and each of the component stocks are increased. You can also use this function if you use the Warehouse Management System (LE-WM).
    Possible special stock indicators:
    None
    Example:
    A box of the structured material S contains 3 pieces of the component K1 and 4 pieces of the component K2. The following material document items result after the material is split at goods receipt:
    Qty Unit Material Movement type
    1 box S 101 +
    1 box S 319 -
    4 piece K1 319 +
    5 piece K2 319 +
    Assign Points Lft hand side

  • BDC to Park the Invoice Document(FV60)  in FI

    hi,
       can any one suggest me how to proced for BDC to Park the Invoice Document(FV60)  in FI.
    thank you .

    Hi,
    Try this BAPI.
    Bapi_incominginvoice_park
    Thanks,
    Anitha

Maybe you are looking for