KKAK - sales document missing

Hi
After we run the KKAK (RA analysis) product cost by sales order, there are some sales order that is suppose to be shown on the report list is missing and not there, can any one let me know why it is missing or not showing up the report?
Thank you

Hello,
If you have an idea which sales orders are missing, try to calculate RA using KKA3. You will get the error.
Since KKAK is for a selection, i would suggest to check your selection criteria and if you are using variants to run KKAK, also check the variant settings. It may so happen that the sales orders what are missing are not collected in selection itself.
Thanks,
Sourabh

Similar Messages

  • Sales documents missing from data base

    Hi
    Their is this unique problem, we have created sales order 'OR'  and saved it, system has generate some document no xxxx
    as soon as we go for billing, system message is
    SD document xxxxxx is not in the database or has been archived
    Message no. V1302
    Diagnosis
    This message is issued if no document header (VBAK) can be found
    (discrepancies in R/3) for a sales requirement single record.
    System Response
    In the initial sales order supply, the following error message appears
    'Document xxxxxx not available'  V1 302.
    Procedure
    If an error occurs in initial data supply in APO, discrepancies have
    occurred between the requirements and sales documents in R/3. This
    discrepance can be corrected in R/3 using report SDRQCR21.
    we have checked after running the report as well, we have chaged the material ans sold and ship to part as well, noting is happening, advice what can be done
    regards
    Niti Narayan

    hi,
    this is to inform you that,
    please check MRP config settigns for the same.
    please check if there is any discrepencies in MRP views of MMR.
    please check from sales order requriment is getting generated in MD04.
    and finally
    run the report to check and correct the discrepencies in SE38,SDRQCR21.
    regards,
    balajia.

  • Missing Records from R/3 Production to BW 3.5 Production (Sales Documents)

    Hi Experts
    I am working on SAP BW 3.5 Version
    When I am Loading data from R/3 Production to BW 3.5 Production half of the Sales Documents are Missing which are start with Alphabetical and I have done right LO-Cokpit procedure properly for
    2LIS_11_VAITM
    2LIS_11_VAHDR
    2LIS_13_VDITM
    2LIS_13_VDHDR
    It Capture only Numerical sales Documents, but there so many alphabetical Sales Documents like
    Ex:
    BPCL-KOCHI
    CHEMPLAST
    DEGREMONT
    E125012800
    F085012605
    Y00P4A010G
    Kindly let me know on urgent basis( why it happens )
    Thanks in Advance
    Suma

    Hi,
    Have you done an init on 11 extractors.
    If not do an init (Filling of the Setup tables) without any selections.
    What I think is happening here is that in your init selections you have put a numerical range for the document numbers. Thats why the alphabetical docs are not comming.
    Check this and let me know if this helps.
    Regards,
    Jadeep

  • Which log file will give the info about what is missing in sales document

    Hello SAP gurus
    I am trying to send a quote from our application to get saved in SAP using .Net Connector. I get the following error messages
    S  V4   233  SALES_HEADER_IN has been processed successfully
    S   V4  233  SALES_ITEM_IN has been processed successfully
    W  V1  555  The sales document is not yet complete: Edit data
    I am looking for any kind of incompletion log that will give more info about what is missing etc.,
    Where can I find such a log. Your feedback will be greatly appreciated.
    Tks
    Ram

    Hi,
    Just check this path.
    Go to sales order->Edit->Incompletion log.
    This  tells your docuement status. If at all your document is incomplete,you can just see what all you are missing.
    Thanks
    KV

  • GL Account Missing While Saving The  Sales document

    Dear Frends
    While POstin the sales document,i am getting error like Gl account missing.This is related to Service Contracts.even i have checked the account determination in VKOA(FI-SD)..
    Kindly give me the solution
    Regards
    Sap Guru
    kischowdary

    Hi,
    Even though the determination is maintained in VKOA check in the determnation analysis if all the keys on which the you have maintained the determination;are recognised by the system.
    If any one particular field is missing then the GL account will not be determined.
    Reward points if useful
    Regards,
    Amrish Purohit

  • Missing Sales document

    Hi,
    While loading delta from 2LIS_11_VAHDR, some of the sales documents are not getting extracted to BW.
    These records are not present in PSA as well.
    However if we fill the setup tables for these documents and do a repair full to BW we are able to load these documents.
    We had added some fields to this extractor and had done a repair full to the first level ODS. That went fine.
    The first delta also went fine. But after that we are able to see that some sales document are not being extracted while delta loading
    Any advices?
    Thanks,
    Pushpa

    Hi Viren
    I will explain the scenario.
    We had to enhance the extractor with field KTEXT which is present in VBAK table.
    We have written a customer exit for that.
    Then to populate this field, we did a repair full.
    The data was correctly populated till here.
    Then while loading deltas, we find that some sales documents are getting skipped.
    In our case suppose 4000 documents are being created in one day then around 100 odd sales document gets missed.
    Thesre is no pattern in the sales record that are getting skipped also.
    These records are not showing in RSA7 also.
    Please let me know what are the possible causes for this.
    Thanks
    Pushpa

  • CRM_ORDER_MISC 020 - Text for sales document is missing

    Hi Experts,
    While replicating from CRM-OLTP the follwing error
    Message no. CRM_ORDER_MISC 020
    Diagnosis
    Errors have occured while transferring the document into another system.
    Transmission log
    Text for sales document type ZNOR is missing in language EN (Notification E V1 119)
    Sales document 0050000062 was not changed (Notification E V4 219)
    Kindly guide me!
    Tks in advance,
    Nivea

    We get this type of error when the data that is send to R/3 is not revalnt for R/3. In your case the text id may not exist in R/3. Pls check you config.

  • Characteristic 0DOC_NUMBER (Sales Document) is missed

    Hi!
    I am working within tcode RSA1 with SAP Solution Manager and have problem to find the the characteristic 0DOC_NUMBER (Sales Document).
    This characteristic Sales Document is a shipped InfoObject of BI Content.
    Does anyone know how to get/import/transport this characteristic?
    Thank you very much!
    regards
    Thom

    I am afraid that is not the case. At least th search for this object was without any result.
    What is the way to install this BI content and how do I get them?
    Thank you very much!
    Hi,
         Only when the BI content is installed, your search will display those objects.
    Goto RSA1 --> BI Content
    (Select "Only Necessar Objects" in the Grouping)
    Now search InoObject in the second pane...
    InfoObject ---> Double Click "Select Objects"
    Search for 0DOC_NUMBER or whatever InfoObject you want to install.
    Select that and "Transfer Selections".
    Click Install ---> Simulate Installation
    If this is in green, then Click Install ---> Install in Background
    Chk the job in SM37. Once the job is successful, go n chk in RSA14 for that infoObject. It will be available now.
    Regards,
    Balaji V

  • Article number is missing for a sales document in VBAP table compared to BW data.

    Hi,
    We are loading data from 2LIS_11_VAITM and 2LIS_11_V_SSL to 0SD_O01, when we execute a report based on this DSO we are getting Article number 2224859 (for example) for sales order 573345 (for example) but when we check in VBAP/VA03 for the same sales order/document (573345)  we don't have the Article Number.
    It is delta load to the DSO from the two datasources and will executed daily once.
    Please suggest me any one on this.

    All,
    Thanks for your replys.
    Here are the more details about this.
    We are using 3.X flow in BW. (3.x Data sources)
    In BW                                           Mapping                In ECC     
    0DOC_NUMBER    Sales document  ----------->  VBELN          Sales Document
    0MATERIAL           Material  -----------------------> MATNR           Article Number
    In VBAP table, I have entered Sales document 573345 and executed then I got so many Article Numbers and Filtered with Article Number 2224859 then got no data.
    As I told earlier in BW for the same Sales Document number we have Article Number.
    We have start routine.
    PROGRAM UPDATE_ROUTINE.
    *$*$ begin of global - insert your declaration only below this line  *-*
    *$*$ end of global - insert your declaration only before this line   *-*
    * The follow definition is new in the BW3.x
    TYPES:
      BEGIN OF DATA_PACKAGE_STRUCTURE.
         INCLUDE STRUCTURE /BIC/CS2LIS_11_VAITM.
    TYPES:
         RECNO   LIKE sy-tabix,
      END OF DATA_PACKAGE_STRUCTURE.
    DATA:
      DATA_PACKAGE TYPE STANDARD TABLE OF DATA_PACKAGE_STRUCTURE
           WITH HEADER LINE
           WITH NON-UNIQUE DEFAULT KEY INITIAL SIZE 0.
    FORM startup
      TABLES   MONITOR STRUCTURE RSMONITOR "user defined monitoring
               MONITOR_RECNO STRUCTURE RSMONITORS " monitoring with record n
               DATA_PACKAGE STRUCTURE DATA_PACKAGE
      USING    RECORD_ALL LIKE SY-TABIX
               SOURCE_SYSTEM LIKE RSUPDSIMULH-LOGSYS
      CHANGING ABORT LIKE SY-SUBRC. "set ABORT <> 0 to cancel update
    *$*$ begin of routine - insert your code only below this line        *-*
    * fill the internal table "MONITOR", to make monitor entries
      LOOP AT DATA_PACKAGE.
        IF DATA_PACKAGE-doc_categ NE 'C' AND
           DATA_PACKAGE-doc_categ NE 'I'.
          DELETE DATA_PACKAGE.
        elseif DATA_PACKAGE-recordmode eq 'R'.
          DATA_PACKAGE-recordmode = 'X'.
          modify DATA_PACKAGE.
        ENDIF.
      ENDLOOP.
    * if abort is not equal zero, the update process will be canceled
      ABORT = 0.
    *$*$ end of routine - insert your code only before this line         *-*
    ENDFORM.
    I think there is no much more lookups. ( I don't have much knowledge in ABAP)
    I have checked in another tables also like VBFA VBAG VBAK, VBKD, VBUK and VBUP but in those tables I don't have Article (MATNR) field.
    One more Question.
    Can any one tell me how the Queued Delta mechanism will work.
    As of now I know that, when ever any changes have been done to the tables this will pickup the changes and move into LBWQ after that RSA7.
    My Question is, If some one has forcefully deleted one Article number from the table for a Sales Order then this Queued delta will pick that also?
    Please let me know If you need any more details

  • Unable to block creation of sales document from Quotation thru user status

    Dear Experts,
    I have maintained a status profile in my Quotation document through the use of user status. I have defined a status to forbid creation of sales document if the status has not yet been set to "Approved".
    However, even when the status is not yet "Approved", it still allows me to create subsequent sales document from this Quotation.
    Anything that I have missed here?

    Hi,
    It should not happen.
    Please check the Object types for which the status profile is created. It should be for either Sales Order header or Sales order Item.
    Make sure that the "create sales document" is "forbiddden" for the initial status only.
    Also please check Low- High numbers for each status.
    Hope this helps.
    Regards,
    Sharan

  • Text Determination Sales document to sales document

    Hi Friends,
    We are configuring text determination sales document to sales document (ZOR to ZLR).
    We have done following configuration:
    1. text type - Z122 ( invoice text header)
    2.) test determination procedure Z1. In text determination procedure Z1 is copy button is enabled. and access seguence 9122 is assigned.
    3. text determination Z1 is assigened to text type Z122.
    4.) text determination is assigned to document type - ZOR.
    let me know what configruation we are missing here.
    While creating sales order we are giving  some description in header text invoice header but the same is not copied to subsequent document ZLR. ( debit memo request).
    We are using this in Resource related billing.( RRB).
    Document flow is
    sales order ( zor)-internal order ( ko01)- Accounting document( fb01)- Resource relating billing doc ( DP91) we generate debit memo request from DP91.
    We need the invoice text entered  in sales order (va01) to copied in debit memo request ( ZLR.)
    We need this at both header and item level.
    kindly suggest.

    Hi,
    Which text determination and text types assigned to ZLR?
    If you maintain- same text type - you can copy
    Thanks
    Chidambaram

  • Explanations on Sales Documents

    Can anybody send explanations about sales documents that I have mentioned below?
    Inquiry     IN
    Quotation     QT
    Free-of-charge delivery     FD
    Standard sales order     OR
    Cash sale     BV
    Rush order     SO
    Quantity contract     CQ
    Maintenance contract     WV
    Rental contract     MV
    Scheduling agreement     DS
    Credit memo request     CR
    Debit memo request     DR
    Subsequent delivery, free-of-charge     SD
    Returns     RE

    hi
    ==============================
    can also refer to the link below for more info on SD ..
    SD Process Flow
    ==============================
    SD FLOW:
    Sales
    Inquiry - A customer’s request to a company that they provide a quotation or sales information without obligation. An inquiry can relate to materials or services, conditions and if necessary delivery dates. The sales area that accepts the inquiry becomes responsible for further processing.
    Quotation - A quotation presents the customer with a legally binding offer for delivering a product or providing a service within certain fixed conditions. This offer is legally binding for the company within a specified time period. A sales area can reply to a customer inquiry with a customer quotation or use it to refer to a business partner contact.
    Sales Order - Request from a customer to a company to deliver a defined quantity of products or provide a service at a certain time.
    The sales area that accepts the inquiry is responsible for completing the agreement.
    Create Delivery:a. Picking - The picking process involves taking goods from a storage location and staging the right quantity in a picking area where the goods will be prepared for shipping.
    b. Packing - Packing is part of delivery- and shipment processing. When you process a delivery, you can select delivery items for packing and assign them to handling units (HUs).
    c. Goods Issue - As soon as the goods leave the company, the shipping business activity is finished. This is illustrated using goods issue for outbound deliveries.
    Billing - Billing represents the final processing stage for a business transaction in Sales and Distribution. Information on billing is available at every stage of order processing and delivery processing.
    Sales Order Management Transactions
    SALES ORDER PROCESSING
    Creating Sales Order - VA01
    Maintaining a Sales Order - VA02
    Displaying a Sales Order - VA03
    Releasing an Order or Delivery from Credit Hold: Non-Flooring - VKM1
    Display List of RMAs by Customer - VA05
    Confirm RMA Goods Receipt - VL02
    Generate list of open return orders for deletion - VA05
    Display Customer returns eligibility - MCSI
    Removing a Billing Block (Approving Credit/Debit Requests) - V.23
    PRICING MASTER DATA
    Create Pricing - VK11
    Creating a Sales Deal - VB21
    Maintaining a Sales Deal - VB22
    Displaying a Sales Deal - VB23
    Maintaining Prices - VK12
    Displaying Prices - VK13
    MATERIAL MASTER DATA
    Creating Material Substitution Master Data - VB11
    Maintaining/Deleting Material Substitution Master Data - VB12
    Displaying Material Substitution Master Data - VB13
    Creating a Bundled Master - MM01
    Creating a Sales BOM - CS01
    Maintaining a Sales BOM - CS02
    Displaying a Sales BOM - CS03
    CUSTOMER MASTER DATA
    Creating Partner Records - XD01
    Maintaining Customer Master Data - XD02
    Displaying Customer Master Data - XD03
    Deactivating a Partner - VD06
    CUSTOMER CREDIT INFO
    Creating/Maintaining New Customer Credit Information - FD32
    Displaying Customer Credit Information - FD33
    Blocking or Unblocking a Customer - VD05
    SHIPPING
    Creating a Delivery - VL01N
    Displaying a Delivery - VL03N
    Changing a Delivery - VL02N
    Shipment Inquiry / Display - VT03
    Adjusting Transfer Order - Confirmation Quantity - LT12
    Collectively Confirm Transfer Order - LT25
    Batch Shipment Confirmation - VL19
    PGI Reversal Cancellation - VL09
    Creating Service Provider/Carrier Master Data - XK01
    Maintaining Serive Provider/Carrier Master Data - XK02
    Displaying Service Provider/Carrier Master Data - XK03
    Maintaining Product Master/Serial # Profile/Unit of Measure/Shipping Unit - MM02
    IDoc Inquiry - WE02 / WE05
    BILLING
    Invoicing a Customer Shipment - VF01
    Reprinting an Invoice - VF31
    Releasing a Sales Order for Billing - V.23
    Creating an Invoice by Using the Billing Due List - VF04
    Checking Open Billing Documents - VF05
    Create Credit/Debit Memo - FB01
    A/R
    Controlling Total Debit/Credit bkgs - F.03
    Generate FI Account balance - F.08
    Generate Month-to-date Inv. register - F.02
    Process payments - FBZ1
    Rqst Individual Customer Corresp. - FB12
    Generate Customer Correspondence - F.61
    Enter Batch totals under Control ttl - FB07
    Display G/L Acct. totals - FBL3N
    Reverse Posted Amounts - FB08
    Customer Refunds - FBL6
    Customer Refund to other than Payer - FB05
    Clearing Debit/Credit on Cust. acct. - FB1D
    Customer Balance in Local Currency - F.23
    G/L Account Balance Report - F.08
    Create Invoice - legal entity adjust - FB01
    Generate Cust. Acct. statements - F.27
    Generate Dunning Letters - F150
    Generate Billing Due List - VF04
    Generate Blocked Billing Doc list - VFX3
    Inq. via Credit Release Screen - VKM1
    List orders by partner - VA05
    Past Due invoices by customer - FD11
    Check number info by G/L account - FBL3N
    Display customer Line items - FBL5N
    SD Configuration:
    Enterprise Structure:
    1. Maintaining Sales Organization
    Sales Organization is an organizational unit responsible for the sale of certain products or services.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check Sales organization
    2. Assigning Sales Organization to Company Code
    This assignment ensures all the sales made through this Sales Organization are accounted for in the assigned Company Code (Company Code is created by FI Consultant).
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign Sales Organziation to Company Code
    3. Maintaining Distribution Channel
    Distribution Channel is the way, in which Products or Services reach Customers.
    IMG -> Enterprise Structure -> Definition -> Sales and Distribution -> Define, copy, delete, check distribution channel
    4. Assigning Distribution Channel to Sales Organization
    This assignment ensures, a Sales Organization can supply Materials to Customers through this Distribution Channel.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution > Assign distribution channel to sales organization
    5. Maintaining Division
    Division is a way of grouping materials, products, or services.
    IMG -> Enterprise Structure -> Definition -> Logistics - General -> Define, copy, delete, check division
    6. Assigning Division to Sales Organization
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign division to sales organization
    7. Setting up Sales Area
    All the sales are made from a particular sales Area. For creating a Sales Order Sales Area is compulsory.
    IMG ->Enterprise Structure -> Assignment -> Sales and Distribution -> Set up sales area
    8. Assigning Sales Organization- Distribution Channel- Plant
    Plant is created ny MM Consultant.
    IMG -> Enterprise Structure -> Assignment -> Sales and Distribution -> Assign sales organization - distribution channel - plant
    9. Define Shipping Points
    Shipping Point is the Organizational element, which is responsible for shipping the Materials to the Customers.
    IMG -> Enterprise Structure -> Definition -> Logistics Execution -> Define, copy, delete, check shipping point
    10 Assigning Shipping Point to Plant
    This assignment ensures that goods from different Plant can be dispatched from different Shipping Points.
    IMG -> Enterprise Structure -> Assignment -> Logistics Execution -> Assign shipping point to plant
    Note: Ensure to do the undermentioned configuration also though it is not in Customizing node of Enterprise Structure.
    11. Defining Common Distribution Channels for Master Data
    Use
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Distribution Channels
    Transaction Code: VOR1
    12. Defining Common Divisions for Master DataUse
    The purpose of this activity is to define distribution channels which have common master data..
    Procedure
    Access the activity using one of the following navigation options:
    IMG Menu -> Sales and Distribution -> Master Data -> Define Common Division
    Transaction Code: VOR2
    Pricing Procedure
    In SD, Pricing Procedure is determined based on Sales Area (Sales Organization + Distribution Centre + Division) + Customer Pricing Procedure + Document Pricing Procedure. Sales Area is determined in Sales Order Header Level. Customer Pricing Procedure is determined from Customer Master. Document Pricing Procedure is determined from Sales Document Type / Billing Type (if configured). Once the pricing procedure is determined, Condition records are fetched. If appropriate condition records are found, the price is determined. If Mandatory pricing condition is missing, system will through an error message.
    In SD, the steps to configure Pricing procedure are as under:
    Step 1:
    Condition table: If existing condition table meets the requirement, we need not create a new condition table. Considering the requirement for new condition table, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Table (select the required fields combination, which will store condition record).
    Step 2:
    Access Sequence: If existing access sequence meets the requirement, we need not create a new access sequence. Considering the requirement for new sequence, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Access Sequence (Access sequence is made up of Accesses (Tables) & the order of priority in which it is to be accessed. Here we assign the condition table to access sequence.
    Step 3:
    Condition Type: If existing condition type meets the requirement, we need not create a new condition type. Considering the requirement for new condition type, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Condition Type. It is always recommended to copy an existing similar condition type & make the neccessary changes. Here we assign Access sequence to Condition type.
    Step 4:
    a. Pricing Procedure: It is recommended to copy a similar pricing procedure & make the neccesary changes in new pricing procedure. Pricing Procedure is a set of condition type & arranged in the sequence in which it has to perform the calculation. Considering the requirement for new Pricing Procedure, the configuration will be done in spro as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Maintain Pricing Procedure.
    b. Pricing Procedure: After maintaining the pricing procedure the next step will be determination of pricing procedure. Configuration for determining pricing procedure in SPRO is as follows: IMG --> Sales & Distribution --> Basic Function --> Pricing Control --> Pricing Procedure --> Determine Pricing Procedure.
    5. Condition record: Condition record is a master data, which is required to be maintained by Core team / person responsible from the client. During new implementation, the condition records can be uploaded using tools like SCAT, LSMW, etc.
    Normal Sales Order Cycle:-
    Step 1: Sales Document Type
    IMG > Sales and Distribution > Sales > Sales Documents >
    Sales Document Header:
    1. Sales Document Type:The sales document types represent the different business transactions, such as Inquiry, Quotation, Sales Order, etc. To create new sales order type, always copy as with reference to similar sales order. If possible use standard sales order.
    2. Define Number Ranges For Sales Documents: Maintain number range with discussion with core team.
    3. Assign Sales Area To Sales Document Types:
    A. Combine sales organizations / Combine distribution channels / Combine divisions: Ensure to maintain these, else Sales Order creation will give error.
    B. Assign sales order types permitted for sales areas: Assign only required Sales Order Types to required Sales Area. This will minimize selection of Sales Order Type as per sales area.
    Sales Document Item:
    1. Define Item Categories: If possible use Standard Item Category. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Item Categories: If possible, use standard. Formula for deriving item category: Sales Document Type + Item Category Group + Usage + Higher Level Item Category = Item Category
    Schedule Line:
    1. Define Schedule Line Categories: If possible use Standard Schedule Lines. Incase if required to create new, copy as from standard & maintain New.
    2. Assign Schedule Line Categories: If possible, use standard. Formula for deriving Schedule Line: Item Category + MRP Type / No MRP Type.
    Step 2:
    IMG > Logistic Execution > Shipping > Deliveries >
    1. Define Delivery Types: If possible use Standard Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Item Categories for Deliveries: If possible use Standard Item Categories for Delivery Type. Incase if required to create new, copy as from standard & maintain New.
    3. Define Number Ranges for Deliveries: Ensure to maintain number range.
    Step 3:
    IMG > Sales and Distribution > Billing >
    1. Define Billing Types: If possible use Standard Billing Type. Incase if required to create new, copy as from standard & maintain New.
    2. Define Number Range For Billing Documents: Ensure to maintain number range.
    3. Maintain Copying Control For Billing Documents: Maintain relevant copy controls such as Sales Order to Billing, Deliver to Billing, etc.
    he configuration differs from scenario to scenario & requirement of the client.
    Interesting &important link to learn much more about configuration & business process is as under:
    Link: http://help.sap.com/
    Path: SAP Best Practices --> Baseline Packages --> Based on SAP ECC 5.00 --> Select Country: for eg, Localized for India --> Technical Information --> Building Blocks --> Select Country for eg, India --> List of Basic Configuration & scenarios will be listed.
    Select the required basic configuration / scenario. These will consist of overview, configuration guide, business process, master data &so on.
    ====
    Cash Sale & Rush Order
    Cash Sales and Rush Orders
    ====
    Contracts
    General Contract Processing
    http://help.sap.com/erp2005_ehp_02/helpdata/en/5e/69a1228f6211d2a9f60000e8a6f09e/frameset.htm
    Renewing Contracts
    http://help.sap.com/erp2005_ehp_02/helpdata/en/2c/275c9c456a11d189440000e829fbbd/frameset.htm
    Subsequent Rental
    http://help.sap.com/erp2005_ehp_02/helpdata/en/42/c820c5f8191377e10000000a1553f7/frameset.htm
    Real Estate Contract
    http://help.sap.com/erp2005_ehp_02/helpdata/en/8d/fb783b05efdb18e10000000a114084/frameset.htm
    Value Contract
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd7a545a11d1a7020000e829fd11/frameset.htm
    Creating and Sending Complaint Notifications
    http://help.sap.com/erp2005_ehp_02/helpdata/en/2a/df32f73d7a4bbd8d6e50b32e9227e8/frameset.htm
    Use of Value Limits (for Unplanned Services)
    http://help.sap.com/erp2005_ehp_02/helpdata/en/c3/72cd0755cd11d189660000e8323c4f/frameset.htm
    ====
    Quantity Contract
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd60545a11d1a7020000e829fd11/frameset.htm
    http://help.sap.com/erp2005_ehp_02/helpdata/en/70/23c791419311d2ac100000e829fbfe/frameset.htm
    Batch Determination in Quantity COntract
    http://help.sap.com/erp2005_ehp_02/helpdata/en/25/283c804f7811d18a150000e816ae6e/frameset.htm
    Customer Contracts
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fd53545a11d1a7020000e829fd11/frameset.htm
    Purchase Contract
    http://help.sap.com/erp2005_ehp_02/helpdata/en/70/23c6ce419311d2ac100000e829fbfe/frameset.htm
    Contract Settlement & Billing
    http://help.sap.com/erp2005_ehp_02/helpdata/en/ea/00efa6f94011d2968c006094b92c6a/frameset.htm
    ====
    Service Contract
    http://help.sap.com/saphelp_sm40/helpdata/en/8f/b4113a7e31e403e10000000a11402f/frameset.htm
    Processing Service Contract
    http://help.sap.com/saphelp_46c/helpdata/en/e6/4a8f849e0311d189b70000e829fbbd/content.htm
    Service Order Processing
    http://help.sap.com/saphelp_crm40/helpdata/en/81/78963ec975667fe10000000a114084/content.htm
    <b>Sub Contracting Cycle</b>
    (1) You have a material that can be procured externally, and you have maintained BOM with components. Any waste generated and received during subcontracting process can be maintained as component with negative quantity. 
    (2) You create a subcontracting PO (PO with Item Category L). You can also maintain Purchase Info Record for Subcontract category for material and subcontractor. 
    (3) You make a transfer posting to issue components for SC PO. Material is sent to subcontractor.  As material remains under your ownership, system does not make any value entry. But quantity is shown as "Material Provided to Vendor" 
    (4) You receive finished material against SC-PO. You also specify components consumed in manufacturing of finished goods. Additionally, if you have negative components in BOM, now you'll also receive subcontracting by-products. There are three events, so three accounting entries are generated: 
    DR FG Stock/ SC By-Product Stock 
    CR Change in Stock (FG/ SC By-Product ) 
    (for finished goods received) 
    DR Subcontracting Charges 
    CR GR/IR Clg 
    (for moneys payable to Subcontractor) 
    DR Consumption (Components) 
    CR Change in Stock (FG/ SC By-Product ) 
    (material provided to Vendor is now charged to expense) 
    (5) You do the IV for SC Invoice, and the process is complete. 
    <b>Process of Subcontract in MM</b>
    Sub-contract business process: 
    You want to buy material from the supplier (processed material/ assembled item) , but for some reason (quality of certain item / price ) you will give some component to vendor . 
    Vendor shall process the item / use the item provided & supply the final item. 
    SAP process: 
    1.Create the finished goods material code. 
    2.Maintain the BOM for the material. 
    3.Create PO with item category as "L" . 
    4.Issue material to vendor with movement type 541 
    5.Receive the material against the PO with movement type 101. 
    6.MIRO to account for vendor's invoice for the service charge& material used by him. 
    Can anybody tell me how a process has to be given to subcontracting?
    Suppose, I have 3 operations  1)weaving 2)dyeing 3)cutting & packing 
    if no 2 process (i.e Dyeing) has to be given to subcontracting, what process should i follow ?
    The following process to be followed for subcontracting. 
    1. Item code(material master) to be created at the stage of before dyeing. 
    2. Item code(material master) to be created after Dyeing as subcontracted item.(F30) 
    3. Bill of material to becreated for the material(2) calling for material(1) 
    4. Inforecord and source list to be created for material(2) with the corresponding vendor 
    5. PO to be released for material (2) 
    6.Along with PO the material(1) to be issued to vendor 
    7.On receipt of material when GR is made the stock with vendor will get updated. 
    <b>How to Create a Subcontract Order?</b>
    To create a subcontract order, proceed as follows: 
    Enter the material you want to order and the item category for subcontracting (L) in the order item. 
    Press ENTER to display the screen for component processing. 
    Enter the components that the vendor requires to manufacture the product. 
    Please note: 
    – You do not need to enter the date required for the components. This date is proposed by the system when you press ENTER. 
    It is calculated as follows:
    Delivery date of the item - Planned delivery time
    – If you do not want the quantity of the components to be changed if the order quantity of the end product is altered, set the indicator Fixed quantity (column F). 
    – You can determine whether the components are available on the date required by selecting Edit -> Availability check. 
    If you entered a bill of material as the material in the subcontract order, the components are created automatically. 
    If you want to determine the components in the bill of material at a later date (for example, if the bill of material is subsequently changed), choose Item -> Component -> New BOM explosion. The existing components are deleted and redetermined in the bill of material. 
    Save the purchase order. 
    When you print the purchase order, the components are printed per order item.
    ====
    Scheduleing AGreements
    Creating Schedule Agreements
    http://help.sap.com/erp2005_ehp_02/helpdata/en/75/ee0f8155c811d189900000e8322d00/frameset.htm
    Controling Scheduling Agrement
    http://help.sap.com/erp2005_ehp_02/helpdata/en/93/7439ee546011d1a7020000e829fd11/frameset.htm
    Example Data
    http://help.sap.com/erp2005_ehp_02/helpdata/en/8a/815cc3b36211d188e70000e8216438/frameset.htm
    Mass Maintenance of Scheduleing Agreements
    http://help.sap.com/erp2005_ehp_02/helpdata/en/1a/8b4bbecdd74536acd4e970faaf6e2d/frameset.htm
    Initial Data Transfer
    http://help.sap.com/erp2005_ehp_02/helpdata/en/49/87c646f4a311d1955100a0c9306667/frameset.htm
    Analysis & Copying of Scheduling Agreements
    http://help.sap.com/erp2005_ehp_02/helpdata/en/45/f9a69036035f4be10000000a114a6b/frameset.htm
    Processing Scheduling Agrements
    http://help.sap.com/erp2005_ehp_02/helpdata/en/bd/1850f298a911d194fc00a0c9306667/frameset.htm
    Scheduling Agreements for Suppliers
    http://help.sap.com/erp2005_ehp_02/helpdata/en/93/743962546011d1a7020000e829fd11/frameset.htm
    ====
    Credit Memo
    Credit Memo
    http://help.sap.com/erp2005_ehp_02/helpdata/en/a8/b99890452b11d189430000e829fbbd/frameset.htm
    Creating Credit Memo / Debit Memo
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/561076545a11d1a7020000e829fd11/frameset.htm
    Creating Credit Memo / Debit Memo Requests
    http://help.sap.com/erp2005_ehp_02/helpdata/en/dd/55fed1545a11d1a7020000e829fd11/frameset.htm
    Credit & Debit Memos
    http://help.sap.com/erp2005_ehp_02/helpdata/en/a2/40418a496e11d3b3850008c719be0f/frameset.htm
    Processing Credit Memo : Example
    http://help.sap.com/erp2005_ehp_02/helpdata/en/4e/b3c399a1f711d194e700a0c9306794/frameset.htm
    ===
    Debit Memo : http://help.sap.com/erp2005_ehp_02/helpdata/en/8d/a4b3880bc4c441905801d5025a5600/frameset.htm
    ====
    Return process
    You need to receipt the rejected goods through SD Module (VA01 - Sales Order type RE). 
    The steps are as follows : 
    1. Create a return request. (Using Sales Order in SD) 
    2. Create outbound delivery according to return request. 
    3. If the setting is correct in the outbound delivery screen SAP will automatically switch post goods issue button into post goods receipt. The setting is in sales order item category and delivery type. 
    4. In the standard system the movement type used is 651. 
    5. After post goods issues receipt is done using outbound delivery, the quantity is placed in blocked stock without value updating. 
    6. You will then decide if the return quantity are indeed bad stock or not. 
    7. Transfer Posting from block stock to unrestricted stock (mvt type 453), this will have accounting effect (Debit Inventory, Credit COGS) 
    8. Goods Issue to scrap account how to create new titles which can be used in creating the "address" view on the Vendor master.{T-Code: XK01} 
    In config go to Basis Components --> basis services --> Address Management --> Maintain title texts 
    Order type (RE)
      Returns (RE) (VA01) Order will be placed as a return type order
         PGR (VL02N) post goods receipt
        Billing (VF01) --> Credit Memo is Raised
    Accounting (VF02) --> Credit memo is passed to Accounting tables
    ===
    Calcelling Invoice.
    VF11 --> PGI (VL09N) 
    ===
    ====
    Reward if USeful
    Thanx & regrads.
    Naren..

  • Problem with copy control from sales document to billing document

    Hi,
    I have a copy control from a sales document to a billing document,
    which is copying everything from the sales document, except the
    conditoin values. Any ideas on why will a copy routine won't copy the
    condition values from a source document? I don't even have a document
    pricing procedure assigned to my billing document. Any setting, that
    we can do to for the conditions to get copied from the sales document
    to the billing document...just as they are in the sales document?
    Thanks for the help in advance.
    Regards,
    Vijay

    In IMG,
    Implementation Guide for R/3 Customizing (IMG)
    -->Sales and Distribution
       -->Billing
          -->Billing Documents
             -->Maintain Copying Control For Billing Documents
                -->Copying control: Sales document to billing document
    What setting do you have for your source sales document type to target billing document type? Select the row that shows the document type you are interested in and double click on item(on the left pane). Select the item category and do display. What value do you see under the 'Pricing Type' and 'Price Source'?
    May be that is where some config setting is missing.
    Srinivas

  • Add fields in Locator result  for Sales Document in GUI (anyone?)

    Dear all,
    I try to find information on how we can customize the locator's result column (especially for Sales document)
    in GUI mode. I know we can Change Layout to choose other available field column to be displayed in the
    locator result. How to add more fields so we can have more fields to choose when we change the layout?
    I searched the SDN CRM forum but no exact answer for this (missed it?)
    In fact, there is a bug on the locator search result when I set field Employee Responsible to be displayed
    on the search result, the system is showing other Partner number instead.
    If you have experienced in add fields on the Change Layout, please kindly share it.
    Appreciate your help (with points)
    Cheers,
    Gun.

    It is GENIL BOL concept and now using WebUI Search.

  • Archiving for Sales Documents

    Hi All,
    I have setup archiving for sales document printout. Did uat in test system no issue but when move to live system, the output type could not be issued. I have set Print and Archive for the output type. The error as below when i view the sales document output. I have setup a ARCH device type in SPAD. But it is still not working. Any idea what config is missing?
    Unknown archiving device
    Message no. PT 040
    Diagnosis
    In archive customizing, you can assign an archive device to an archive. Otherwise, the value from the profile parameter 'rspo/default_archiver' is used, or the default value 'ARCH'. However, none of these devices exist.
    Procedure
    Maintain an appropriate device in Transaction SPAD.
    Thanks
    Dyl

    Hi,
    See whether this link helps in tackiling the issue.
    ftp://ftp.software.ibm.com/software/dw/dm/db2/0308kammerer/CommonstoreSAPArchive.pdf
    Regards,
    Saju.S

Maybe you are looking for