Manual reorder point  planning not able to create

Dear all,
I am maintaining  manual reorder point planning for one raw material  with MRP type  VB and  also maintained reorder point level . For other two raw materials  i am maintaining  MRP type as  PD  my issue  is
when ever  i run MRP for FG material  purchase requisition is not generating for the material with MRP type VB even though stock is less than Reorder point. For other two raw materials  purchase requisitions are generated 
Pls give me solutions for  generating the purchase requisitions  for the raw material with MRP type  VB.
                                                            Thanks
                                                             MBR

please check here:
http://help.sap.com/saphelp_47x200/helpdata/en/f4/7d256344af11d182b40000e829fbfe/frameset.htm

Similar Messages

  • Manual Reorder point planning stock is not showing in MD04

    HI,
       Would any one help me when i plan for reorder point planing the details furnished below.
    Mrp type: V1
    Lot size :HB
    ROP : 30
    Max stock level :1000
    in Material master settings.But when i run the MRP using MD03 system is not showing available stock in MD04.It is showing 0 stock rather it would show 4 (MMBE un restricted stock..)
    What are thesettings required or any thing missing in IMG. Please help me in this.
    Regards,
    Srini

    Srini,
    You may also want to check if the Unrestricted stock is in a storage location that is excluded from MRP.
    On MD04 you will then see a separate line item at storage location & the Qty =4 should appear as shown below.
    12/02/2009     Unrest Stock                                                       12           12      
    12/02/2009     SLocSt     QANN StLoc: not plnd          0           8     QANN
    12/02/2009     SLocSt     VEND StLoc: not plnd          0           0      VEND
    Hope this helps. Good lcuk.
    thanks,
    Ramm

  • Manual reorder point planning

    Hi Friends, Can anybody please convey complete procedure of manual Reorder pointplanning step by step including T codes. Full points will be awarded....
    Edited by: k prasanna on Aug 1, 2008 12:57 PM

    Hi,
    1. MM02 - MRP 1 view, here enter MRP Type - VB, Lot Size - EX and then enter Quantity for Reorder Point generation
    2. MD02 - MRP Run for Material with following Parameters
    Material
    Plant
    Processing key          NETCH               Net change for total horizon
    Create purchase req.    1                   Purchase requisitions
    Delivery schedules      3                   Schedule lines
    Create MRP list         1                   MRP list
    Planning mode           3                   Delete and recreate planning data
    Scheduling              1                   Basic dates will be determined for plann
    Activate all "Process Control Parameters"
    And then Press Enter.
    System will give Planned Order/Purchase Req. if Stock of Material falls below the Reorder Point.
    Also put some stock for the material so that you can analyze it in better way.

  • Difference :Automatic Reorder Point Planning and Forecast based palning ?

    Dear MM Guru's,
    As we See in throtical Concepts that
    Automatic Reorder point planning and Forcast Based Planning Used the prevuious Historical Data.
    Please explain what is difference Between them.
    regards,
    A. S.

    Hi,
    Reorder Point Planning: -
    Use: -
    In reorder point planning, procurement is triggered when the sum of plant stock and firmed receipts falls below the reorder point.
    Features: -
    The reorder point should cover the average material requirements expected during the replenishment lead time.
    The safety stock exists to cover both excess material consumption within the replenishment lead time and any additional requirements that may occur due to delivery delays. Therefore, the safety stock is included in the reorder level.
    The following values are important for defining the reorder point:
    - Safety stock
    - Average consumption
    - Replenishment lead time
    The following values are important for defining the safety stock:
    - Past consumption values (historical data) or future requirements
    - Vendor/production delivery timelines
    - Service level to be achieved
    - Forecast error, that is, the deviation from the expected requirements
    Manual Reorder Point Planning
    In manual reorder point planning, you define both the reorder level and the safety stock level manually in the appropriate material master.
    Automatic Reorder Point Planning
    In automatic reorder point planning, both the reorder level and the safety stock level are determined by the integrated forecasting program.
    The system uses past consumption data (historical data) to forecast future requirements. The system then uses these forecast values to calculate the reorder level and the safety stock level, taking the service level, which is specified by the MRP controller, and the material's replenishment lead time into account, and transfers them to the material master.
    Since the forecast is carried out at regular intervals, the reorder level and the safety stock level are continually adapted to the current consumption and delivery situation. This means that a contribution is made towards keeping stock levels low.
    Forecast-Based Planning: -
    Use: -
    Forecast-based planning is also based on material consumption. Like reorder point planning, forecast-based planning operates using historical values and forecast values and future requirements are determined via the integrated forecasting program. However, in contrast to reorder point planning, these values then form the basis of the planning run. The forecast values therefore have a direct effect in MRP as forecast requirements.
    Features: -
    The forecast, which calculates future requirements using historical data, is carried out at regular intervals. This offers the advantage that requirements, which are automatically determined, are continually adapted to suit current consumption needs. The forecast requirement is reduced by the material withdrawal so that the forecast requirement quantity that has already been produced is not included in the planning run again.
    Reducing Forecast Requirements
    - Reducing forecast requirements by consumption
    If consumption is higher than the forecast requirements in the current month, then the system also reduces future forecast requirements.
    - Reducing current forecast requirements by consumption
    If consumption is higher than the forecast requirements in the current month, then the system does not reduce future forecast requirements.
    - Average reduction of the forecast requirements
    The reduction of the forecast requirements is based on average daily consumption. Actual consumption data is not relevant.
    The system calculates the average daily requirement first using the formula forecast requirement/number of workdays in the forecast period.
    The forecast requirements are then reduced by the quantity resulting from the following formula: number of workdays worked x average daily requirements.
    Period Pattern and Forecast Periods
    You can specify the period pattern for the forecast (daily, weekly, monthly or per accounting period) and the number of periods to be included in the forecast individually for each material. It is possible, however, that the forecast period pattern is not specific enough for planning purposes. In this case, you can define per material that the forecast requirements should be divided according to a finer period pattern for planning. You can also define how many forecast periods are to be taken into account during requirements planning. The splitting indicator is defined in Customizing for MRP per plant and per period unit and is assigned to the material in the material master.
    Example: -
    For a monthly forecast, the requirements date would be set on the first workday of the month because, for planning, it is assumed that the total requirement must be available at the beginning of the period. You can then divide this monthly requirement into either daily or weekly requirements.

  • I am not able to create database manually.unexpected error incountered why?

    I am not able to create database manually.unexpected error incountered why?
    Same step is worked in another system
    SQL> startup nomount
    ORACLE instance started.
    Total System Global Area 97589952 bytes
    Fixed Size 453312 bytes
    Variable Size 46137344 bytes
    Database Buffers 50331648 bytes
    Redo Buffers 667648 bytes
    SQL> ed
    Wrote file afiedt.buf
    1 CREATE DATABASE icici
    2 LOGFILE GROUP 1 ('F:\oracle\oradata\icici\logfile\redo01.log') SIZE 10M,
    3 GROUP 2 ('F:\oracle\oradata\icici\logfile\redo02.log') SIZE 10M,
    4 GROUP 3 ('F:\oracle\oradata\icici\logfile\redo03.log') SIZE 10M
    5 MAXLOGFILES 5
    6 MAXLOGMEMBERS 5
    7 MAXLOGHISTORY 1
    8 MAXDATAFILES 10
    9 MAXINSTANCES 1
    10 CHARACTER SET US7ASCII
    11 NATIONAL CHARACTER SET AL16UTF16
    12 DATAFILE 'F:\oracle\oradata\icici\datafile\system01.dbf' SIZE 100M REUSE
    EXTENT MANAGEMENT LOCAL
    13 DEFAULT TEMPORARY TABLESPACE tempts1 TEMPFILE 'F:\oracle\oradata\icici\d
    atafile\temp01.dbf' SIZE 100M REUSE
    14 UNDO TABLESPACE undotbs DATAFILE 'F:\oracle\oradata\icici\datafile\undot
    bs01.dbf'SIZE 100M REUSE
    15* AUTOEXTEND ON NEXT 5120K MAXSIZE 300M
    SQL> /
    CREATE DATABASE icici
    ERROR at line 1:
    ORA-01092: ORACLE instance terminated. Disconnection forced
    SQL>

    Check the alert log. Paste the end of the file over here.
    Yoann.

  • Reorder Point Planning

    Hi all,
    Business Process is:
    1. I am having 6 plants assigned to a single company code.
    2. I had created material "A" and assinged to all 6 plants with
    different manual reorder points, selected MRP type VB,.
    Plants:                    1000      1010    1020    1030    1040    1050
    Sloc                        A100     B100    C100       D100   E100   F100
    reorder point      100         20        30       25        18       32
    i have defined all MRP plant parameters for individual plants:
    From my central stores A100 at Plant 1000 the stock will be issued to remaining all Plants, so central stores-in-charge will run an MRP daily or weekly, as we have set different reorder points for the same material at receiving plants
    (1010, 1020,1030,1040,1050) so system first triggers the shortfall at all receiving plants and later triggers the Supplying Plant 1000.
    Requirements:
    1. If the avaialability stock at sloc B100 at Plant 1010 is 15, after running MRP the system is able to create an Auto PR for 5 quantity,. so its working fine,,,,
    but my client requirement is:
    if the avaialability stock at various plants are:
    Plants:         1000      1010   1020   1030   1040   1050
    Sloc        A100     B100   C100  D100   E100   F100
    reorder point   100         20       30      25      18        32
    avail stock          250         15       40      32      29        35
    diff stock      +150          -5     +10      +7    +11       +3
    so if we observe the above table,,, we can see the difference stock (Avail stock - reorder point) now if my stores-in-charge runs an MRP, a PR for 5 quantity at Plant 1010 is generated, however we are having excess stock at different plants.
    what we want is, if my stores-in-charge runs an MRP, no PR should be generated to any Plant except a message saying that at particualr Plants(1020,1030,1040,1050) there are excess quantity of (10,7,11,3) at their individual storage locations.
    i am not having much idea about MRP run,,,  
    1. how to map the above business process in system?
    2. if i use planned order concept, ie. during MRP run a Planned Order for a Plant will be generated later my stores in charge will convert this planned order to purchase requisition based on the stock availabile at different plants? so how to work with planned orders/
    3. Can i do total mrp run for all plants (1000,1010,1020,1030,1040) at a time?
    can any one please help me out,,, its urgent.
    regards,
    urendra

    Hi all,
    1.  In OM0E i have defined planning scope and assigned 6 plants as sequence.
    2.  In MD01, i have selected the same planning scope, create purchase requisitions - planned orders,  i have'nt selected any Plants.
    3. system has given a msg that planning run scope is only possible through parellel mode,  now i have selected the parallel processing check box.
    4. after pressing enter,, system gvs me the following msg,,,
    Please check the destinations for parallel MRP
    Message no. MD251
    Diagnosis
    No destinations have been entered in Customizing or none of the the destinations (application server) entered are active.
    In Customizing for MRP, you define the logical destinations (servers) to be used for parallel processing.
    how to overcome this,,,
    regards,
    urendra

  • Regarding reorder point planning.

    Hi experts,
    I have entered safety stock as 40 pcs., reorder point 50 and created requirement for
    may 09 - 30 pcs.
    jun-09 - 30 pcs.
    After executing MRP run it is showing planned order for 50 pcs. only.
    But the requirements are not covered I mean to say at last the available qty should be zero.
    Please help me on this immediately.
    Rgds,
    Parul.

    In Consumption based planning(re-order point planning), planned independent requirements or dependent requirement will not be considered in the net requirements calculation. Instead, it is triggered when stock levels fall below a predefined reorder point .So, all the planned independent or dependent requirements in a certain period of time should have been considered before setting the reorder point
    Therefore, these planning procedures are used in areas  for planning both B- and C-parts and operating supplies.(low value materials, but consumption is more)
    In reorder point planning, SAP checks whether the available stocks are below the reorder point that has been set for the material. If they are, SAP will create procurement proposal.
    We can determine the reorder point manually (u201CVB-Manual reorder point planningu201D MRP Type in standard SAP R/3) or, it can also be calculated automatically using the material forecast (u201CVM-Automatic reorder point planningu201D MRP Type in standard SAP R/3).
    In standard SAP R/3 system, besides u201CVB u2013 Manual Reorder Pointu201D and u201CVM u2013 Automatic Reorder Pointu201D MRP Types, there are also other MRP Types that have reorder point as its basis to calculate requirement with additional procedure which count external requirement (sales order and manual reservation) as a requirement. The MRP Type are: u201CV1-Manual reorder point with external requirementsu201D and u201CV2-Automatic reorder point with external requirementsu201D.
    If you want to include requirements in the reorder point calculation in addition to the customer requirements and manual reservations,
    go to SPRO ->Materials management ->consumption based planning ->master data -> MRP Types
    Select the mrp type v1 and
    select the following fields:
    o     Requirements for materials to be provided in subcontracting
    o     Dependent order reservations on the basis of production orders
    o     Dependent order reservations on the basis of maintenance orders or networks
    o     Release orders
    o     Purchase requisition releases
    o     Forecast delivery schedules
    regards,
    sikkandar basha

  • Reorder Point Planning via SNP heuristics based on ACTUAL stock

    Hi All,
    In R/3 there is the option in reorder point planning to take into account external requirements (MRP type V1) or not to take into account external requirements (VB). When using reorder point planning in APO SNP Heuristics, the reorder point is being determined in time based on the PROJECTED stock (so taking into account external requirements) so the result is the same as in R/3 when using MRP type V1. In the future horizon, everytime the projected stock goes below the reorder point, a replenishment is triggerd via a planned order or purchase requisition.
    I would like to know if (and how) it is possible to perform reorder point planning in APO SNP via heuristics (can be location or network) only taking into account the ACTUAL stock (and no external requirements in the past or in the future). So, the same behavior as the MRP type VB in R/3. The difference is that only on the short term, 1 time replenishment is triggered (via planned order or purchase requisition) if the current stock is below the reorder point.
    Remarks: this needs to be able to be set product specific, because not all products at the location will need to use this logic.
    Any help or thoughts for a solution direction (preferably without programming or user exits) are appreciated.
    Thanks in advance,
    Dennis

    If you really just want a pure re-order point scenario based on current stock, I'd suppose that you'd want to create a new data view and modify the total demand macro so that it doesn't generate any sort of future requirements (total demand will essentially be zero).  Then the reorder point will be the only thing driving planning when compared to the initial bucket SOH, which is presumably calculated through the standard macro and according to the stock cat. group you indicate in the location/product master.
    You could set some specific filter in the material master using the MATLOC freely definable attributes to create selection profiles and govern in which data view you process the planning for certain materials.  That is to say, you'd assign all materials which are pure current stock ROP and tag them with some attribute and use that to create selections for your Heuristic variants.

  • Lot quantity to order for a material set as reorder point planning

    Dear All,
    Suppose the requirements of a material are as follows:
    Week1 Required quantity - 100
    Week2 required quantity - 150
    Week3 required quantity - 300
    Week4 required quantity - 500
    This material is set as "VB" (Reorder point planning in the material master)
    My questions is:
    Can we use periodic lot sizing procedure for a material planned based on reorder point planning , so that MRP run will consider the requirements of a month (1050) and use that as the lot size to order material.
    We want to plan the material if it falls below the reorder level, but we want the system to dynamically calculate the quantity to order based on the actual demand (and not on either fixed lot size or maxmimum stock level).
    with regrds
    Laxmipathi.G.V

    Hi
         Use Anyone of the following
    1. Use automatic reorder point with forecast planning requirment.Where ssytem will calculate reorder point automatically based on weekly /monthly Forecast req.In this case Lot size you can use EX itself.
    2. Use Planning type PD and lot size EX and Instaed of ROL use safety stock so that system will consider weekly sale req. and  also safety stock according to that procerement proposal will be created.
    Regards,
    Velmurugan S

  • Dependant requirements are to be considered in reorder point planning

    Hi,
    We are currently using safety stock planning with PD.but the problem is that MRP triggers a procuement proposal when ever the availabile quantity(not the stock) falls below safety stock(as it considers MRP elements like DEP REQ etc in the net requirements calculation).
    Now if i propose VB,it does not consider the dependent requirements at all(they are not even displayed)
    Requierment is that the procurement proposals should only be triggered when the safety stock falls below the physical stock and DEPREQ's and all other requirements should still be displayed.
    I appreciate your help in getting me through with this.Thanks.
    Ram

    Dear Ram,
    go to the customizing of MRP type ,
    ther you will find the field 'Reorder point planning with external requirements'
    Indicates whether an external requirement (sales order or manual reservation) is included in the net requirements calculation for reorder point planning.
    If yes, you can decide whether it is to be included:
    -in the complete planning horizon, or
    -only within the replenishment lead time
    I hope the above information will be useful,
    best regards

  • Rescheduling in Reorder point planning V1

    Hi,
    I have a requirement for a material 2/7/2009 and I do not have any stock for it. The MRP type for it is V1 (Manual reord.point w. ext.reqs) and reorder point is 85.
    Now when I run MRP today ie., 4/1/2009, a planned order with a date of 4/7/2009 is generated without rescheduling date or exception.
    Why is the planned order without rescheduling date or exception?
    Sincerely,
    Ketan

    Hi, 
    When planning with reorder levels, system generates the planned orders but it would not give an exception message. This is due to the fact that with reorder level planning, you are trying to replenish the stock by maintaining the stock levels & you are not looking at any particular demand or requirement to be included in the MRP calculations. As you mentioned erlier that running with MRP type PD it gives out excpetion messages as MRP there is looking at the requirements & gives out exceptions.
    Hope this explains the reasons for not getting the exception messages.
    Regards
    Vineet

  • Not able to create sales order  using BAPI - BAPI_SALESORDER_CREATEFROMDAT2

    Hi Experts,
    I am not able to create sales order . I am using BAPI - BAPI_SALESORDER_CREATEFROMDAT2
    to create sales order .I am passing external sales order number to the parameter
    SALESDOCUMENTIN.
    I am getting following error.
    "524   |Only quantity 1 EA is allowed (Item 00001"
    Here EA is UOM(Unit of measurement).
    Below is the sample program through which i am trying to create the sales order.
    *& Report  ZSDC_SALES_TEST
    report  zsdc_sales_test.
    *DATA: wa_bapi_header    TYPE bapisdhd1.
    Include Name    - ZSDC_SALES_ORD_UPLOAD_TOP
    Program Name    - ZSDC_SALES_ORD_UPLOAD_1393
    Program Title   - Include for Data Declaration  and selection screen
    Created by      - Lalitha W
    Created on      - 18-Nov-2008
    Object ID       - SD_C_1393_SALES_ORDER_UPLOAD
    Request Id      - SD3K905579
    Description - This is a common INCLUDE for data declarations and
    *selection screen details.
                            HISTORY
    Date    |Developer |Req by    | Description              |Reference ID
            |          |          |                          |
            |          |          |                          |
                               TYPE-POOLS
    *TYPE-POOLS: truxs, abap, slis.
                              TABLES
    *TABLES: t100.
                               TYPES
    types:begin of   ty_header,
            auart(4)    type c,    " Sales Order Type
            vkorg(4)    type c,    " Sales Organization
            vtweg(2)    type c,    " Distrubution Channel
            spart(2)    type c,    " Division
            kunnr_1(10) type c,    " Sold to Party
            kunnr_2(10) type c,    " Ship to Party
            augru(3)    type c,    " Order Reason
            bstkd(35)   type c,    " PO Number
            bstdk(10)   type c,    " PO Date
            ketdat(10)  type c,    " Required Delivery Date
            zterm(4)    type c,    " Payment Terms
            inco1(3)    type c,    " Inco Terms -1
            inco2(28)   type c,    " Inco Terms -2
            prsdt(10)   type c,    " pricing date
            waerk(5)    type c,    " Document Currency
            vkbur(4)    type c,    " Sales Office
            vkgrp(3)    type c,    " Sales group
            pltyp(2)    type c,    " Price List type
            kdgrp(2)    type c,    " Customer Group
            bstkd_e(35) type c,    " Ship-to-party PO number
            submi(10)   type c,    " Collective Number
            bname(35)   type c,    " Name
            ihrez(12)   type c,    " Your Reference
            kschl_1(4)   type c,    " Condition Type
            kbetr_1(11)  type c,    " Amount
            kschl_2(4)   type c,    " Condition Type
            kbetr_2(11)  type c,    " Amount
            kschl_3(4)   type c,    " Condition Type
            kbetr_3(11)  type c,    " Amount
           partner_1(25) TYPE c,    "  Partner(Bill To Party Number)
           partner_2(25) TYPE c,    "  Partner(Payer Number)
           partner_3(25) TYPE c,    "  Partner(Sales Responsible Number)
           partner_4(25) TYPE c,    "  Partner(Order admin)
           partner_5(25) TYPE c,    "  Partner(Contact person)
            partner_1(10) type c,    "  Partner(Bill To Party Number)
            partner_2(10) type c,    "  Partner(Payer Number)
            partner_3(10) type c,    "  Partner(Sales Responsible Number)
            partner_4(10) type c,    "  Partner(Order admin)
            partner_5(10) type c,    "  Partner(Contact person)
            tdspras_1(2)  type c,
            text_1(500)   type c,    " Text Before Items Z012
            tdspras_2(2)  type c,
            text_2(500)   type c,    " Invocie Up Z034
            tdspras_3(2)  type c,
            text_3(500)   type c,    " Invocie Down Z035
            tdspras_4(2)  type c,
            text_4(500)   type c,    " Customer Reference Continue Z018
            tdspras_5(2)  type c,
            text_5(500)   type c,    " Dispatch Marks/ Order Z019
            tdspras_6(2)  type c,
            text_6(500)   type c,    " Ordered By  Z003
            tdspras_7(2)  type c,
            text_7(500)   type c,    " Sales Parameters Z002
            kvgr1(3)      type c,    " Industry
            kvgr2(3)      type c,    " customer BU
    end of ty_header.
    types: begin of ty_item,
              bstkd(35)     type c,    " PO Number
              bstdk(10)     type c,    " PO Date
              bstkd_e(35)   type c,    " Ship-to-party PO number
              posnr(6)      type c,    " POSTION NUMBER
              matnr(18)     type c,    " Material Number
              kwmeng(18)    type c,    " Order Quantity
              pstyv(4)      type c,    " Sales doc. item categ
              kursk(18)     type c,    " EXCHANGE RATE****
              ffprf(8)      type c,    " DIP PROFILE
              werks(4)      type c,    " Delivering Plant
              vstel(4)      type c,    " SHIPPING POINT
              lgort(4)      type c,    " STORAGE LOCATION
              route(6)      type c,    " Route
              kurrf(18)     type c,    " EXCHANGE RATE-FI
              ntgew(18)     type c,    " Net Weight
              brgew(18)     type c,    " Gross Weight
              gewei(3)      type c,    " Weight Unit
              prctr(10)     type c,    " profit center
              abgrs(6)      type c,    " RESULT ANALYSIS KEY
              kalsm_k(4)    type c,    " COSTING SHEET
              kschl_1(4)    type c,    " Condition Type
              kbetr_1(11)   type c,    " Amount
              kschl_2(4)    type c,    " Condition Type
              kbetr_2(11)   type c,    " Amount
              kschl_3(4)    type c,    " Condition Type
              kbetr_3(11)   type c,    " Amount
              text_1(500)    type c,    " material Text 0001
              tdspras_1(1)   type c,
              text_2(500)    type c,    " Pr Text 9001
              tdspras_2(1)   type c,
           end of ty_item.
    types:  begin of ty_schedule_line,
             bstkd(35)       type c, "PO number
             bstdk(10)       type c, "PO date
             bstkd_e(35)     type c, "Ship-to-party PO number
             posnr(6)        type c, "sales doc.Item
             etdat(10)       type c, "Schedule line date
             wmeng(2)        type c, "Order Quantity
            end of ty_schedule_line.
    types: begin of ty_err  ,
            auart(4)    type c,    " Sales Order Type
            vkorg(4)    type c,    " Sales Organization
            vtweg(2)    type c,    " Distrubution Channel
            spart(2)    type c,    " Division
            kunnr_1(10) type c,    " Sold to Party
            kunnr_2(10) type c,    " Ship to Party
            augru(3)    type c,    " Order Reason
            bstkd(35)   type c,    " PO Number
            bstdk(10)   type c,    " PO Date
            ketdat(10)  type c,    " Required Delivery Date
            zterm(4)    type c,    " Payment Terms
            inco1(3)    type c,    " Inco Terms -1
            inco2(28)   type c,    " Inco Terms -2
            prsdt(10)   type c,    " pricing date
            waerk(5)    type c,    " Document Currency
            vkbur(2)    type c,    " Sales Office
            vkgrp(3)    type c,    " Sales group
            pltyp(2)    type c,    " Price List type
            kdgrp(2)    type c,    " Customer Group
            bstkd_e(35) type c,    " Ship-to-party PO number
            submi(10)   type c,    " Collective Number
            bname(35)   type c,    " Name
            ihrez(12)   type c,    " Your Reference
            kschl_1(4)   type c,    " Condition Type
            kbetr_1(11)  type c,    " Amount
            kschl_2(4)   type c,    " Condition Type
            kbetr_2(11)  type c,    " Amount
            kschl_3(4)   type c,    " Condition Type
            kbetr_3(11)  type c,    " Amount
            partner_1(25) type c,    "  Partner(Bill To Party Number)
            partner_2(25) type c,    "  Partner(Payer Number)
            partner_3(25) type c,    "  Partner(Sales Responsible Number)
            partner_4(25) type c,    "  Partner(Order admin)
            partner_5(25) type c,    "  Partner(Contact person)
            tdspras_1(2)  type c,
            text_1(500)   type c,    " Text Before Items Z012
            tdspras_2(2)  type c,
            text_2(500)   type c,    " Invocie Up Z034
            tdspras_3(2)  type c,
            text_3(500)   type c,    " Invocie Down Z035
            tdspras_4(2)  type c,
            text_4(500)   type c,    " Customer Reference Continue Z018
            tdspras_5(2)  type c,
            text_5(500)   type c,    " Dispatch Marks/ Order Z019
            tdspras_6(2)  type c,
            text_6(500)   type c,    " Ordered By  Z003
            tdspras_7(2)  type c,
            text_7(500)   type c,    " Sales Parameters Z002
            kvgr1(3)      type c,    " Industry
            kvgr2(3)      type c,    " customer BU
            message(600) type c,
      end of ty_err.
    types: begin of ty_t685a,
            kschl type kschl,
            krech type krech,
          end of ty_t685a.
                       INTERNAL TABLES
    ***header
    data:  g_krech_1(4)    type c,    " Calculation type for condition
           g_krech_2(4)    type c,    " Calculation type for condition
           g_krech_3(4)    type c.    " Calculation type for condition
          g_krech_4(4)    TYPE c,    " Calculation type for condition
          g_krech_5(4)    TYPE c,    " Calculation type for condition
          g_krech_6(4)    TYPE c,    " Calculation type for condition
          g_krech_7(4)    TYPE c,    " Calculation type for condition
          g_krech_8(4)    TYPE c,    " Calculation type for condition
          g_krech_9(4)    TYPE c,    " Calculation type for condition
          g_krech_10(4)   TYPE c,    " Calculation type for condition
          g_krech_11(4)   TYPE c,    " Calculation type for condition
          g_krech_12(4)   TYPE c,    " Calculation type for condition
          g_krech_13(4)   TYPE c,    " Calculation type for condition
          g_krech_14(4)   TYPE c,    " Calculation type for condition
          g_krech_15(4)   TYPE c,    " Calculation type for condition
          g_krech_16(4)   TYPE c,    " Calculation type for condition
          g_krech_17(4)   TYPE c,    " Calculation type for condition
          g_krech_18(4)   TYPE c,    " Calculation type for condition
          g_krech_19(4)   TYPE c,    " Calculation type for condition
          g_krech_20(4)   TYPE c.    " Calculation type for condition
    Items
    data:   g_krech_item_1(4)   type c,    " Calculation type for condition
            g_krech_item_2(4)   type c,    " Calculation type for condition
            g_krech_item_3(4)   type c.    " Calculation type for condition
           g_krech_item_4(4)   TYPE c,    " Calculation type for condition
           g_krech_item_5(4)   TYPE c,    " Calculation type for condition
           g_krech_item_6(4)   TYPE c,    " Calculation type for condition
           g_krech_item_7(4)   TYPE c,    " Calculation type for condition
           g_krech_item_8(4)   TYPE c,    " Calculation type for condition
           g_krech_item_9(4)   TYPE c,    " Calculation type for condition
           g_krech_item_10(4)  TYPE c,    " Calculation type for condition
           g_krech_item_11(4)  TYPE c,    " Calculation type for condition
           g_krech_item_12(4)  TYPE c,    " Calculation type for condition
           g_krech_item_13(4)  TYPE c,    " Calculation type for condition
           g_krech_item_14(4)  TYPE c,    " Calculation type for condition
           g_krech_item_15(4)  TYPE c,    " Calculation type for condition
           g_krech_item_16(4)  TYPE c.    " Calculation type for condition
    data: it_t685a  type standard table of ty_t685a.
    data: wa_bapi_header    type bapisdhd1,
         wa_bapi_headerx   TYPE bapisdhd1x,
          it_bapi_item      type table of bapisditm,
         it_bapi_itemx     TYPE TABLE OF bapisditmx,
          it_bapi_cond      type table of bapicond,
         it_bapi_condx     TYPE TABLE OF bapicondx,
          it_bapi_partner   type table of bapiparnr,
          it_bapi_shdl      type table of bapischdl,
         it_bapi_shdlx     TYPE TABLE OF bapischdlx,
         it_bapi_order_text type TABLE OF BAPISDTEXT,
          it_bapireturn     type table of bapiret2.
    data:  wa_bapi_item       like line of it_bapi_item,
          wa_bapi_itemx      LIKE LINE OF it_bapi_itemx,
           wa_bapi_cond       like line of it_bapi_cond,
          wa_bapi_condx      LIKE LINE OF it_bapi_condx,
           wa_bapi_partner    like line of it_bapi_partner,
           wa_bapi_shdl       like line of it_bapi_shdl,
          wa_bapi_shdlx      LIKE LINE OF it_bapi_shdlx,
          wa_bapi_order_text like LINE OF it_bapi_order_text,
           wa_bapireturn      like line of it_bapireturn.
    *DATA: zmode(1) VALUE 'N'.
    data: it_header      type standard table of ty_header.
    *DATA: it_temp_header TYPE STANDARD TABLE OF ty_header.
    data: it_item        type standard table of ty_item.
    *DATA: it_temp_item   TYPE STANDARD TABLE OF ty_item.
    data: it_err         type standard table of ty_err.
    data: it_fline1 type standard table of tline,
          wa_fline1 type tline.
    data: it_thead1 type thead.
    data: it_fline2 type standard table of tline,
          wa_fline2 type tline.
    data: it_thead2 type thead.
    data: it_fline3 type standard table of tline,
          wa_fline3 type tline.
    data: it_thead3 type thead.
    data: it_fline4 type standard table of tline,
          wa_fline4 type tline.
    data: it_thead4 type thead.
    data: it_fline5 type standard table of tline,
          wa_fline5 type tline.
    data: it_thead5 type thead.
    data: wa_header         like line of it_header,
          wa_item           like line of it_item,
          wa_err            type ty_err,
         wa_bill           LIKE LINE OF it_bill,
         wa_bill1          LIKE LINE OF it_bill,
          wa_iterr          like line of it_err,
          wa_t685a          like line of it_t685a.
         wa_bill_item TYPE ty_bill_item.
    data: it_schedule_line  type standard table of ty_schedule_line,
          wa_schedule_line type ty_schedule_line.
    data: sales_order_no     type bapivbeln-vbeln.
    data: ext_sales_order_no type bapivbeln-vbeln.
    Variable to be used to separate the fields which are concatenated by a
    runtime character
    *DATA: g_tabchar(1) TYPE c VALUE cl_abap_char_utilities=>horizontal_tab.
    *DATA: wa_truxs_t_text_data TYPE truxs_t_text_data.
    *DATA: g_filename      TYPE string,
         g_path          TYPE string,
         g_fullpath      TYPE string,
         g_user_action   TYPE i,
         g_file_encoding TYPE abap_encoding.
    *DATA : g_text(8192),
    data : g_mstring1(100) type c,
          g_mstring2(100) type c,
          g_mstring3(100) type c,
          g_mstring4(100) type c,
          g_mstring5(100) type c.
    data: g_count1 type ebelp,
          g_str_count1(6) type c.
    data: g_count type ebelp,
          g_str_count(6) type c.
    *DATA: f_subrc      LIKE sy-subrc,
         f_subrc1     LIKE sy-subrc,
         f_error(500) TYPE c,
         item1(27)    TYPE c,
         item2(27)    TYPE c,
         item3(27)    TYPE c,
         item4(27)    TYPE c,
         i            TYPE ekpo-ebelp.
    *DATA: g_billplan_header TYPE c,
         g_billplan_item TYPE c.
    data : g_external_so type vbak-vbeln. "SO
                          SELECTION-SCREEN
    selection-screen begin of block frame1 with frame title text-001 .
    parameters:p_file1 type rlgrap-filename, "OBLIGATORY, "Header data.
               p_file2 type rlgrap-filename, "OBLIGATORY, "Item Data.
               p_file3 type rlgrap-filename,            "Schedule line.
               p_file4 type rlgrap-filename ."OBLIGATORY. "Error file.
    selection-screen end of block frame1.
    start-of-selection.
      wa_bapi_header-doc_type     =  'Z0MX'. "order type
      wa_bapi_header-sales_org    =  '0130'."sales org
      wa_bapi_header-distr_chan   =  '13'.  "distr channel
      wa_bapi_header-division     =  '13'.  "division
    Old code from copied program
    wa_bapi_header-purch_no_s   =  wa_header-kunnr_2.  " Ship to party
    New code as required in Finland project
    We are using to Header ->Order Tab -> Ship to Party -> Purchase order no (BSTKD_E) to store Old legacy SO number
      wa_bapi_header-purch_no_s   =  'MX100443'.  "External SO i.e Old legacey SO number
      wa_bapi_header-ref_1_s      = '0000666666'. "Sold to party
    wa_bapi_header-ord_reason   =  wa_header-augru.
      wa_bapi_header-purch_no_c   =  'ddr1234'.    " PO number
      wa_bapi_header-purch_date   =  sy-datum.    " PO date
      wa_bapi_header-req_date_h   =  sy-datum.   " Required Delivery Date
      wa_bapi_header-pmnttrms     =  '01'.    " Payment Terms
    wa_bapi_header-incoterms1   =  wa_header-inco1.
    wa_bapi_header-incoterms2   =  wa_header-inco2.
    wa_bapi_header-price_date   =  wa_header-prsdt.    " Pricing date
    wa_bapi_header-currency     =  wa_header-waerk.    " Document Currency
    wa_bapi_header-sales_grp  =  wa_header-vkgrp. " Sales group
    wa_bapi_header-price_list   =  wa_header-pltyp. " Price list type
    wa_bapi_header-cust_group   =  wa_header-kdgrp.   " Cust Group
    wa_bapi_header-ship_type    =  wa_header-vsart.   " Shipping Type
    wa_bapi_header-purch_no_s   =  wa_header-bstkd_e. " Ship-to-party po number
    wa_bapi_header-collect_no   =  wa_header-submi.   " Collective No.
    wa_bapi_header-name         =  wa_header-bname.   " Name
    wa_bapi_header-ref_1        =  wa_header-ihrez.   " Your Reference
    wa_bapi_header-cust_grp1    =  wa_header-kvgr1.   " Industry
    wa_bapi_header-cust_grp2    =  wa_header-kvgr2.   " Customer BU
    *ENDFORM.                    " f_header
    IF wa_header-partner_1 IS NOT INITIAL.
        wa_bapi_partner-partn_role = 'AG'.
        wa_bapi_partner-partn_numb = '0000666666'.
        wa_bapi_partner-itm_number = '000000'.
        append wa_bapi_partner to it_bapi_partner.
        clear wa_bapi_partner.
    ENDIF.
      call function 'CONVERSION_EXIT_ALPHA_INPUT'
        exporting
          input  = wa_header-partner_2
        importing
          output = wa_header-partner_2.
    IF wa_header-partner_2 IS NOT INITIAL.
        wa_bapi_partner-partn_role = 'WE'.
        wa_bapi_partner-partn_numb = '0000666666'.
        wa_bapi_partner-itm_number = '000000'.
        append wa_bapi_partner to it_bapi_partner.
        clear wa_bapi_partner.
    ENDIF.
      perform f_item.
    data : order_items_inx type table of bapisditmx with header line.
      order_items_inx-material          = 'X'.  "
      order_items_inx-target_qty        = 'X'.  "
      order_items_inx-comp_quant        = 'X'.  "
      order_items_inx-trgqty_den        = 'X'.
      order_items_inx-rnddlv_qty        = 'X'.
    order_items_inx-updateflag = 'I'.
    order_items_inx-target_qu = 'X'.
      order_items_inx-plant             = 'X'.  "
      append order_items_inx.
      call function 'BAPI_SALESORDER_CREATEFROMDAT2'
        exporting
          salesdocumentin = 'MX11111152'
      order_header_in      = wa_bapi_header
             order_header_inx     = wa_bapi_headerx
      importing
      salesdocument        = sales_order_no
      tables
      return               = it_bapireturn
      order_items_in       = it_bapi_item
      order_items_inx      =  order_items_inx
      order_partners       = it_bapi_partner
       order_conditions_in  = it_bapi_cond.
      if sy-subrc is initial.
      commit work.
      endif.
    *&      Form  f_item
          text
    form f_item .
      call function 'CONVERSION_EXIT_ALPHA_INPUT'
        exporting
          input  = wa_item-posnr
        importing
          output = wa_item-posnr.
      wa_item-posnr = '000010'.
    IF sy-subrc EQ 0. "IS INITIAL.
      move wa_item-posnr to g_str_count."commented out by shakti
    ENDIF.
      wa_bapi_item-itm_number        =  wa_item-posnr.  " Line item
    WA_BAPI_ITEM-PO_ITM_NO         =  WA_ITEM-EBELP.
    wa_bapi_item-division          = wa_item-spart.
      wa_bapi_item-purch_no_c        = 'ddr1234'.   " po number
      wa_bapi_item-purch_date        = sy-datum.   " po date
      wa_bapi_item-purch_no_s        = 'MX11111112'. " Ship-to-party po number
      wa_item-matnr = 'MAXIMO_SERVICE'.
      call function 'CONVERSION_EXIT_MATN1_INPUT'
        exporting
          input        = wa_item-matnr
        importing
          output       = wa_item-matnr
        exceptions
          length_error = 1
          others       = 2.
      if sy-subrc is initial.
        wa_bapi_item-material        = wa_item-matnr.  "material
      endif.
      wa_bapi_item-target_qty        = '1'. " Order qty
      wa_bapi_item-comp_quant = '1'.
      wa_bapi_item-target_qu = 'EA'.
        wa_bapi_item-fixed_quan = '1'.
    wa_bapi_item-comp_quant        = wa_item-kwmeng.
    wa_bapi_item-trgqty_den        = '1'.
    wa_bapi_item-rnddlv_qty        = wa_item-kwmeng.
    CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
       EXPORTING
         input  = wa_item-ps_psp_pnr
       IMPORTING
         output = wa_item-ps_psp_pnr.
    IF sy-subrc = 0.
       wa_bapi_item-wbs_elem          = wa_item-ps_psp_pnr.
    ENDIF.
      wa_bapi_item-item_categ        = 'ZMAX'.
    wa_bapi_item-ex_rate_fi        = wa_item-kurrf.
    wa_bapi_item-dli_profil        = wa_item-ffprf.   " Dynamic item processor profile
    wa_bapi_item-route             = wa_item-route.   " route
    wa_bapi_item-exchg_rate        = wa_item-kursk.
      wa_bapi_item-plant             = '2090'.   " Plant
      wa_bapi_item-ship_point        = 'FN11'.   " Shipping point
    wa_bapi_item-store_loc         = wa_item-lgort.   " stg loc
    REPLACE ALL OCCURRENCES OF  ',' IN wa_item-ntgew WITH '.'.
    REPLACE ALL OCCURRENCES OF  ',' IN wa_item-brgew WITH '.'.
    wa_bapi_item-net_weight        = wa_item-ntgew.  "
    wa_bapi_item-gross_wght        = wa_item-brgew.  "
      call function 'CONVERSION_EXIT_CUNIT_INPUT'
        exporting
          input    = wa_item-gewei
          language = sy-langu
        importing
          output   = wa_item-gewei.
       EXCEPTIONS
         unit_not_found = 1
         OTHERS         = 2.
    IF sy-subrc <> 0.
    ENDIF.
      wa_bapi_item-untof_wght        =  'KG'.  " weight unit
      replace all occurrences of  ',' in wa_item-kursk with '.'.
      replace all occurrences of  ',' in wa_item-kurrf with '.'.
    wa_bapi_item-profit_ctr        = wa_item-prctr.   " Profit center
    wa_bapi_item-resanalkey        = wa_item-abgrs.   " RESULT ANALYSIS KEY
    wa_bapi_item-cstg_sheet        = wa_item-kalsm_k. " COSTING SHEET
      append wa_bapi_item to it_bapi_item.
    endform.                    " f_item
    Thanks & regards,
    Chetan

    see the following to create sales order:-
    *& Report  ZSALESORDER
    *&DEVELOPED BY JANI KRUPA 4.10.2008
    REPORT  ZSALESORDER.
    Parameters
    Sales document type
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text FOR FIELD p_auart.
    PARAMETERS: p_auart TYPE auart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Sales organization
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text1 FOR FIELD p_vkorg.
    PARAMETERS: p_vkorg TYPE vkorg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Distribution channel
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text2 FOR FIELD p_vtweg.
    PARAMETERS: p_vtweg TYPE vtweg OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Division.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text3 FOR FIELD p_spart.
    PARAMETERS: p_spart TYPE spart OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Sold-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text4 FOR FIELD p_sold.
    PARAMETERS: p_sold  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Ship-to
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text5 FOR FIELD p_ship.
    PARAMETERS: p_ship  TYPE kunnr OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    SKIP 1.
    Material
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text6 FOR FIELD p_matnr.
    PARAMETERS: p_matnr TYPE matnr   OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Quantity.
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text7 FOR FIELD p_menge.
    PARAMETERS: p_menge TYPE kwmeng  OBLIGATORY.
    SELECTION-SCREEN END OF LINE.
    Plant
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text9 FOR FIELD p_plant.
    PARAMETERS: p_plant TYPE werks_d .
    SELECTION-SCREEN END OF LINE.
    Complete Deliver
    SELECTION-SCREEN BEGIN OF LINE.
    SELECTION-SCREEN COMMENT 2(20) v_text10 FOR FIELD p_autlf.
    PARAMETERS: p_autlf TYPE autlf DEFAULT 'X'.
    SELECTION-SCREEN END OF LINE.
    Data declarations.
    DATA: v_vbeln            LIKE vbak-vbeln.
    DATA: header             LIKE bapisdhead1.
    DATA: headerx            LIKE bapisdhead1x.
    DATA: item               LIKE bapisditem  OCCURS 0 WITH HEADER LINE.
    DATA: itemx              LIKE bapisditemx OCCURS 0 WITH HEADER LINE.
    DATA: partner            LIKE bapipartnr  OCCURS 0 WITH HEADER LINE.
    DATA: return             LIKE bapiret2    OCCURS 0 WITH HEADER LINE.
    DATA: lt_schedules_inx   TYPE STANDARD TABLE OF bapischdlx
                             WITH HEADER LINE.
    DATA: lt_schedules_in    TYPE STANDARD TABLE OF bapischdl
                             WITH HEADER LINE.
    DATA: lt_schedules_ink    TYPE STANDARD TABLE OF bapisdhead1
                             WITH HEADER LINE.
    Initialization.
    INITIALIZATION.
    v_text   = 'Order type'.
    v_text1  = 'Sales Org'.
    v_text2  = 'Distribution channel'.
    v_text3  = 'Division'.
    v_text4  = 'Sold-to'.
    v_text5  = 'Ship-to'.
    v_text6  = 'Material'.
    v_text7  = 'Quantity'.
    v_text9  = 'Plant'.
    v_text10 = 'Complete delivery'.
    Start-of-selection.
    START-OF-SELECTION.
    Header data
    Sales document type
      header-doc_type = p_auart.
      headerx-doc_type = 'X'.
    Sales organization
      header-sales_org = p_vkorg.
      headerx-sales_org = 'X'.
    Distribution channel
      header-distr_chan  = p_vtweg.
      headerx-distr_chan = 'X'.
    Division
      header-division = p_spart.
      headerx-division = 'X'.
      headerx-updateflag = 'I'.
    *Complete delivery
        header-COMPL_DLV = p_autlf.
        header-COMPL_DLV = 'X'.
    Partner data
    Sold to
      partner-partn_role = 'AG'.
      partner-partn_numb = p_sold.
      APPEND partner.
    Ship to
      partner-partn_role = 'WE'.
      partner-partn_numb = p_ship.
      APPEND partner.
    ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000010'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
    item category
      itemx-ITEM_CATEG = 'X'.
      APPEND item.
      APPEND itemx.
      ITEM DATA
      itemx-updateflag = 'I'.
    Line item number.
      item-itm_number = '000020'.
      itemx-itm_number = 'X'.
    Material
      item-material = p_matnr.
      itemx-material = 'X'.
    Plant
      item-plant    = p_plant.
      itemx-plant   = 'X'.
    Quantity
      item-target_qty = p_menge.
      itemx-target_qty = 'X'.
      APPEND item.
      APPEND itemx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000010'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000010'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
      Fill schedule lines
      lt_schedules_in-itm_number = '000020'.
      lt_schedules_in-sched_line = '0001'.
      lt_schedules_in-req_qty    = p_menge.
      APPEND lt_schedules_in.
      Fill schedule line flags
      lt_schedules_inx-itm_number  = '000020'.
      lt_schedules_inx-sched_line  = '0001'.
      lt_schedules_inx-updateflag  = 'X'.
      lt_schedules_inx-req_qty     = 'X'.
      APPEND lt_schedules_inx.
    Call the BAPI to create the sales order.
      CALL FUNCTION 'BAPI_SALESDOCU_CREATEFROMDATA1'
           EXPORTING
                sales_header_in     = header
                sales_header_inx    = headerx
           IMPORTING
                salesdocument_ex    = v_vbeln
           TABLES
                return              = return
                sales_items_in      = item
                sales_items_inx     = itemx
                sales_schedules_in  = lt_schedules_in
                sales_schedules_inx = lt_schedules_inx
                sales_partners      = partner.
    Check the return table.
      LOOP AT return WHERE type = 'E' OR type = 'A'.
        EXIT.
      ENDLOOP.
      IF sy-subrc = 0.
        WRITE: / 'Error in creating document'.
      ELSE.
    Commit the work.
        COMMIT WORK AND WAIT.
        WRITE: / 'Document ', v_vbeln, ' created'.
      ENDIF.

  • Not able to create Follow up transaction since it has been grayed out

    Hi Experts,
    We have a scenario where in we will create the Sales Transactions (OR) in ECC and then it will replicates to CRM.
    In CRM we wants to create Returns Order (RE) as a follow up Transaction to OR (which is replicated from ECC to CRM) .
    When I tried to create Returns Order (RE) in CRM as a follow up document to Sales Transaction (OR), the follow up Transaction CRM Returns (RE) has been grayed out. I mean it is in display mode only.
    And then I created Sales Transaction (OR) in CRM itself and then I tried to create follow up Returns Transaction (RE) I was able to create.
    But I am not able to Create Returns Order (RE) for the Sales Transactions (OR) that have been replicated from ECC to CRM.
    Can anybody help me in resolving this issue. Any help ful answer will be rewarded with points.
    Thanks in advance,
    -Frederick Johnson.

    Hi Fredrick,
    Please check, whether you have completed all the steps for Copying Control for Business Transactions in the following path in IMG:
    SPRO->Customer Relationship Management->Transactions->Basic Settings->Copying Control for Business Transactions:
    - Define Copying Control for Transaction Types
       In this step, you define the control for copying business transaction types.
       To do this, you enter a source tranaction type and a target transaction type, and define the corresponding conditions for this combination.
    - Define Copying Control for Item Categories
    In this step, you define the control for copying item categories.
    To do so, you enter a source item category and a target item category, and define the corresponding conditions.
    - Define Item Category Determination when Copying
    In this step, you define a specific item category determination which should be run during copying. The item category is used to find the target item category in the source transaction for the transaction type in the target transaction. This means that the transaction type for the source transaction is not relevant for the item category determination.
    If the system cannot find an entry for the copying transaction in this table, the item category is found in the target transaction using the normal item category determination.
    This might help you
    regards
    Srikantan

  • I installed ios 7 in iphone 4 - i am not able to create event in calender ,   icon is not active

    i installed ios 7 in iphone 4 - i am not able to create event in calender ,   icon is not active

    You will have to upgrade your operating system version and possibly your whole computer.  We cannot provide more information easily until we know more about your system.
    Get more information about your computer. Go to the Apple in the upper left corner of any window, then "About This Mac", then "More Info..."  Copy and paste the information here, but omit the serial number and Hardware UUID (if present).
    Apple does tell you about required equipment for the iPhone -- in 8 point medium gray type on a light gray box.   The Store associates kind of automatically assume everybody is running a new model computer and the one I met when we bought our iPhone had never seen a pre-2008 Mac and was somewhat puzzled why anybody would own such an antique.

  • Not able to create new entry in RSADMIN Table

    Hi All,
            I am going thru the OSS note 1275837  (Note 1275837 - PrecServer: process based load distribution (ABAP part)), as it recommends
            add the entry "BWPREC_USE_NEW_LOAD" with value "X" in table "RSADMIN"
          When I check in SE11 and SE16 there is no option to create button for above entry in table RSADMIN.
          Please advise for any help to create above entry.
    Thanks
    Ganesh Reddy.
    Edited by: Ganesh Reddy on Jan 11, 2010 4:20 PM
       I got access key from our basis team. But still not able to create new entry as mentioned in OSS note. Any further help....
    Thanks
    Ganesh Reddy.
    Edited by: Ganesh Reddy on Jan 11, 2010 9:13 PM

    Hi
    Goto SM30 - Table Maintanance Generator and enter the table name and click on button maintain ,it will show the error message
    "The maintenance dialog for RSADMIN is incomplete or not defined" because the table maintenance is not allowed manually.
    First Option
    When you double click the error message  a performance assistant screen will open in that you can see Procedure
    "Generate the required maintenance dialog" click on that and try to maintain the table using Access Key, as i dont have access key i have not tried this option.
    Second Option
    You can write an SE38 program with an insert statement.
    TABLES rsadmin.
    DATA: wa TYPE rsadmin.
    wa-object = 'object name'.
    wa-value = 'X'.
    INSERT into rsadmin values wa.
    Thanks

Maybe you are looking for

  • Link in banner shud open in new window!!

    i have added an image which connects to my parents or main site (which is different from current on which i am working on) now when i click on this it is opening in the same page, i want to open it in new window how to do it? pl. note i don't want us

  • How can I test (Abap) a session is from type RFC

    Hi , How can I test (Abap) a session is from type RFC ? Field in SY tables ?

  • AT NEW  CHAR FIELD

    Hello Experts I have an ITAB in which there atre fields name salary age and company  . i have sorted the dataon the basis of copmany and age I need to print the data for each company seperately . there are total 40 records .and 4 copmanies . i need t

  • Function module to send mails to outlook

    Hi All, Can you let me know if there is an FM to send mails to the OUTLOOK. Also let me know what parameters need to be passed to the FM. I need to send mails to the individual and also to the user group. Regards Shiva

  • How to display menu bar in safari

    New to IOS.  Just bought an iPad. Trying to import bookmarks, but need to have a menu in Safari to do it (according to some instructions I'm using) Don't see a switch in Settings.