Restriction of creating p.o with refe. to service P.R

Dear cons
There is no restriction of creating service P.O with reference to service P.R in our company. That means we can create as many number of ser. P.O under one P.R. In case of material P.R restiction has been activated.how can we solve the problem in service P.R.

HI,
You mean to say, You want to have the restriction to the servive PO also.
How you have activated to the material PO. Is it with the help of BADI or any thing else.
The same you can make use along with doc type you are using for the service PO.
If I understood wrongly pl let me know.
regards,
Kannaiah Naidu

Similar Messages

Problem creating process order with ref of sale order

Dear all,
Kindly give solution for this scenerio..............................
I am creating Process Order with ref of sale order manually in cor1. In the COR1 screen copy from field i gave my ref sale order, so that particualr order and batch is assigned to that order only.
My problem was suppose if sale order is created for 10 tonns, but my batch size and resource capacity is 2 tonns only. so first time i change my batch quantity 2 tonns instead of 10 tonns and created my order and confirmed.
if i go to second time the same process i am doing creating process order with ref of same sale order but it comes again 10 tonns instead of 8 tonns. why it comes like this already i confirmed 2 tonns in this sale order?
my requirement is if any process order is created with ref of any sale order and again if i am creating any process order with ref of same sale order left quantity only system should show.
for this what i have to do kindly help to this
regards,
s.sakthivel

Dear KK,
Pls check whether ZKIN, ZKQT, ZKOR have all the properties similar to IN, QT, OR respectively. If they are different, please ensure that you know the reason why they are different. This check has to be done at tcode VOV8
Some fields like sales document category, Transaction group, screen seq group, Doc pricing procedure need to be similar to the parent document unless you know why you have changed them.
Once this check is done, check the copy controls in VTAA. Before that try creating these documents separately without reference. This shoudl work fine only after which you need to check copy control. If this is not working fine, then there is some problem with the document type settings in VOV8. Testing this is possible only if Reference mandatory field is left empty. Make sure that is properly configured.
Once this is done, check copy controls in VTAA. You can just copy the copycontrol between IN and QT and QT and OR and create for ZKIN to ZKQT and ZKQT to ZKOR.
Once this is done, check whether your item category settings are properly done , also the schedule line settings. The tcodes are VOV7, VOV6, VOV4, VOV5 etc.
Now check whether your material master and customer master are consistent with the item category settings(Item category group).
Now create the transaction. It shoudl work fine.
Reward if this helps.

Inbound idoc to create outbound delivary with ref to sales order

Hi,
       I am getting and inbound idoc from the external party to create Inbound delivary with reference to sales order.
       But my inbound process code FM(IDOC_INPUT_DESADV1) checking PO no. and item which is NON SAP PO no. and item in idoc. So, it is giving error PO doesnot exist in the system .
       I want to create Inbound delivary with ref to SO not with reference to PO.
        Pls check techincal details which i am using for inbound process :
        Process code : DELS
        Inbound FM    : IDOC_INPUT_DESADV1
        Message type : DESADV
         Idoc : DELVRY05
        Kindly help me.
Regards,
Manoj

Hi,
For creating inbound Purchase Orders, you can use Idocs PORDCR1.PORDCR101 or PORDCR1.PORDCR102. I have used this and they are working perfectly for us.
Reg,
NJ

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Error while creating sales order with ref using SD_SALESDOCUMENT_CREATE

Hi
I am creating sales order with reference using function module SD_SALESDOCUMENT_CREATE , while creating i am getting error
Document doesn't have document category even thougth i am passing document category in header as well as item lavel.
In VBUK table there is no value for VGTYP.
Can you please help me how to resolve it.
Thanks & regards
kiran

Problem resolved by passing REFDOC_CAT in the FM along with SD_DOC_CAT.
Thanks

Create sales order with ref to quotation - usage of line items not copied

hi
i have created a quotation for which the first line item(higher level item) is a configurable item for which the value of the field use (vbap-vkaus) is blank and the line items the use field is given as 'HIDE DISCOUNT'.
when i created a order with reference to the above quotation i am not getting the value "HIDE DISCOUNT" populated for the line items for usage field ..
can any one knows any user exit / data transfer routine please suggest me
thanks in advance
rajani yeluri

hi
i have created a quotation for which the first line item(higher level item) is a configurable item for which the value of the field use (vbap-vkaus) is blank and the line items the use field is given as 'HIDE DISCOUNT'.
when i created a order with reference to the above quotation i am not getting the value "HIDE DISCOUNT" populated for the line items for usage field ..
can any one knows any user exit / data transfer routine please suggest me
thanks in advance
rajani yeluri

Issue in creating sales order with ref contract(quantity)

hi friends,
I am creating sales order with reference contract using
"BAPI_SALESORDER_CREATEFROMDAT1"
my issue is with quantity field when i am entering quantity as 1 then it is taking as 0.001
i am also declaring its unit field too but there is no change.
in my program i am taking quantity as parameter.
field description is like this Order qty in sales units - 00009001 corresponds to 9.001
is there any chance of changing the quantity .
please help.

There is another similar post...look at those comments. Consider the data types in use...in true numeric fields with decimals, the decimal is implied, so look at how you're sending and/or converting any value.... For instance, if I were sending data to a quantity field described as curr 15, decimals 3, I would expect that I needed to send 1.000 (or perhaps 1000, depending on my testing) in the input to get a quantity of 1.

Create sales order with reference to service order

Hi
I need to create sales order based on the service order . Is there any BAPI function module available for this ?
Please help...
Regards
Sujith

**　プログラムＩＤ　　　　　　 ： ZBAPI_SALESORDER_CREATE               *
**　プログラム名称　　    　　 ： Upload Sales Order Creation                   *
**　処理概要　　　　　　　   　：                                       *
**　作成者　　　　　　　　　　 ： Karthik.P                             *
**　作成日　　　　　　　　　　 ： 2006/08/10                            *
REPORT ZBAPI_SALESORDER_CREATE LINE-SIZE 132 MESSAGE-ID ZMMBAPI .
       Internal table definition                                     *
****<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>>>
DATA: GT_ORDER_HEADER_IN LIKE BAPISDHD1,
*******<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
      GT_ORDER_HEADER_INX LIKE    BAPISDHD1X,
*****<<<<<Return Parameter>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
      GT_RETURN LIKE BAPIRET2 OCCURS 0 WITH HEADER LINE, " Return Messages
*********<<<Communication Fields: Sales and Distribution Document Item<>>>>>
      GT_ORDER_ITEMS_IN LIKE BAPISDITM OCCURS 0 WITH HEADER LINE, " Item Data
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
      GT_ORDER_ITEMS_INX LIKE BAPISDITMX OCCURS 0 WITH HEADER LINE, "Item Data Checkbox
*********<<<Communication Fields: Sales and Distribution Document Item>>>>>>>
      GT_SALESDOCUMENT LIKE BAPIVBELN-VBELN , "Number of Generated Document
*********<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
      GT_ORDER_PARTNERS LIKE BAPIPARNR OCCURS 0 WITH HEADER LINE, "Document Partner
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
      GT_ORDER_SCHEDULES_IN LIKE BAPISCHDL OCCURS 0 WITH HEADER LINE, "Schedule Line Data
****<<<<<<<<Checkbox List for Maintaining Sales Document Schedule Line>>>>>>>>
      GT_ORDER_SCHEDULES_INX LIKE BAPISCHDLX OCCURS 0 WITH HEADER LINE, " Checkbox Schedule Line Data
*******Communication Fields for Maintaining Conditions in the Order
      GT_ORDER_CONDITIONS_IN LIKE BAPICOND OCCURS 0 WITH HEADER LINE,
******Communication Fields for Maintaining Conditions in the Order
      GT_ORDER_CONDITIONS_INX LIKE BAPICONDX OCCURS 0 WITH HEADER LINE.
       Data definition                                               *
DATA: BEGIN OF GT_FT_SALES OCCURS 0,
       DOC_TYPE(4) ,        "Sales Document Type
       SALES_ORG(4) ,        "Sales Organization
       DISTR_CHAN(2) ,      "Distribution Channel
       DIVISION(2)   ,       "DIVISION(2)
       SALES_DIST(6) ,      "Sales district
       INCOTERMS1(3) ,      "Incoterms (part 1)
       INCOTERMS2(28) ,     "Incoterms (part 2)
       PMNTTRMS(4) ,        "Terms of payment key
       PRICE_DATE(8) ,       "Date for pricing and exchange rate
       PURCH_NO_C(35) ,     "Customer purchase order number
       PURCH_NO_S(35) ,     "Ship-to Party's Purchase Order Number
       EXCHG_RATE(8) ,      "Directly quoted exchange rate for pricing and statistics
       CURRENCY(5) ,         "SD document currency
       MATERIAL(18),         "MATERIAL
       TARGET_QTY(13) ,     "Target quantity in sales units
       ITEM_CATEG(4) ,      "Sales document item category
       MATL_GROUP(8) ,      "Material Group
       PURCH_NO_C1(35),      "Customer purchase order number
       SALES_DIST1(6) ,     "Sales district
       INCOTERMS11(3) ,     "Incoterms (part 1)
       INCOTERMS21(28),     "Incoterms (part 2)
       PMNTTRMS1(4) ,     "Terms of payment key
       EXCHG_RATE1(8) ,    "Directly quoted exchange rate for pricing and statistics
       PRICE_DATE1(8) ,    "Date for pricing and exchange rate
       TRG_QTY_NO(5)    , "Factor for converting sales units to base units (target qty)
       DIVISION1(2)     ,                                   "DIVISION1
       SALQTYNUM(5)     , "Numerator (factor) for conversion of sales quantity into SKU
       GROSS_WGHT(3)    , "Gross Weight of the Item
       NET_WEIGHT(15)    , "Net Weight of the Item
       UNTOF_WGHT(3)    ,"Weight Unit
       PARTN_ROLE(2)   ,"Partner function
       PARTN_NUMB(10)   ,"Customer Number 1
********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
       ITM_NUMBER(6) ,"Item number of the SD document
       REQ_QTY(8) , "Schedule line date
       DLV_DATE(8) , "Schedule line date
       MS_DATE(8) , "Material availability date
       LOAD_DATE(8) , "Loading time (local time with reference to a shipping point)
       GI_DATE(8), "Time of goods issue (local DATE, with reference to a plant)
       TP_DATE(8) , "Transportation planning -time (local w/ref. to shipping pnt)
       ITM_NUMBER2(6) , "Condition item number
END OF GT_FT_SALES,
       MSG(240) TYPE C, " Return Message
       E_REC(8) TYPE C,    " Error Records Counter
       REC_NO(8) TYPE C, " Records Number Indicator
       S_REC(8) TYPE C,   " Successful Records Counter
       T_REC(8) TYPE C.   " Total Records Counter
selection block for EXCEL UPLOAD FILE>>>>>>>>>>>>>>>>>>>>>>>>
SELECTION-SCREEN BEGIN OF BLOCK B1 WITH FRAME TITLE TEXT-000.
PARAMETERS FILE TYPE IBIPPARMS-PATH OBLIGATORY.
SELECTION-SCREEN END OF BLOCK B1.
*<<<<AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .>>>>>>>>>>>>
AT SELECTION-SCREEN ON VALUE-REQUEST FOR FILE .
CALL FUNCTION 'F4_FILENAME'
    EXPORTING
      PROGRAM_NAME = SYST-CPROG
      DYNPRO_NUMBER = SYST-DYNNR
    IMPORTING
      FILE_NAME     = FILE.
**<<<<<<<<<<<<<<<<<START-OF-SELECTION.>>>>>>>>>>>>>>>>>>>>>>>>>>>
START-OF-SELECTION.
CALL FUNCTION 'WS_UPLOAD'                                 "#EC *
    EXPORTING
      FILENAME                = FILE
      FILETYPE                = 'DAT'
    TABLES
      DATA_TAB                = GT_FT_SALES
    EXCEPTIONS
      CONVERSION_ERROR        = 1
      FILE_OPEN_ERROR         = 2
      FILE_READ_ERROR         = 3
      INVALID_TYPE            = 4
      NO_BATCH                = 5
      UNKNOWN_ERROR           = 6
      INVALID_TABLE_WIDTH     = 7
      GUI_REFUSE_FILETRANSFER = 8
      CUSTOMER_ERROR          = 9
      NO_AUTHORITY            = 10
      OTHERS                  = 11.
IF SY-SUBRC <> 0 .
    MESSAGE E000.
ENDIF.
SKIP 3.
FORMAT COLOR COL_HEADING INVERSE ON.
    WRITE 40 TEXT-001.
FORMAT COLOR COL_HEADING INVERSE OFF.
SKIP 1.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
    WRITE :/ TEXT-002, 13 SY-MANDT , 104 TEXT-003, 111 SY-UNAME,
              / TEXT-004, 13 SY-DATUM , 104 TEXT-005, 111 SY-UZEIT.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
SKIP 3.
LOOP AT GT_FT_SALES.
      PERFORM SLALE_UPLOAD_DATA.
ENDLOOP.
T_REC = E_REC + S_REC.
SKIP 3.
FORMAT COLOR COL_TOTAL INVERSE ON.
    WRITE: /38 TEXT-007, T_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
FORMAT COLOR COL_NEGATIVE INVERSE ON.
    WRITE: /38 TEXT-008, E_REC.
FORMAT COLOR COL_NEGATIVE INVERSE OFF.
FORMAT COLOR COL_TOTAL INVERSE ON.
    WRITE: /38 TEXT-009, S_REC.
FORMAT COLOR COL_TOTAL INVERSE OFF.
*&      Form SLALE_UPLOAD_DATA
      text
--> p1        text
<-- p2        text
FORM SLALE_UPLOAD_DATA .
*******<<<<<<<<<<Communication Fields: Sales and Distribution Document Header>>>>>>
    GT_ORDER_HEADER_IN-DOC_TYPE =    'TA'.
    GT_ORDER_HEADER_IN-SALES_ORG = GT_FT_SALES-SALES_ORG . "'0001'
    GT_ORDER_HEADER_IN-DISTR_CHAN = GT_FT_SALES-DISTR_CHAN. "'01'
    GT_ORDER_HEADER_IN-DIVISION =   GT_FT_SALES-DIVISION. " '01'
    GT_ORDER_HEADER_IN-SALES_DIST = GT_FT_SALES-SALES_DIST ."'000001'
    GT_ORDER_HEADER_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1. "'CFR'
    GT_ORDER_HEADER_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
    GT_ORDER_HEADER_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS .    "'0001'
    GT_ORDER_HEADER_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE ."'20060818'
    GT_ORDER_HEADER_IN-PURCH_NO_C = '32'.
    GT_ORDER_HEADER_IN-PURCH_NO_S =   '32'.
    GT_ORDER_HEADER_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE ."'1.00000'
    GT_ORDER_HEADER_IN-CURRENCY = GT_FT_SALES-CURRENCY . " 'EUR'
********<<<Checkbox Fields for Sales and Distribution Document Header>>>>>>>>>
    GT_ORDER_HEADER_INX-DOC_TYPE   = 'X'.
    GT_ORDER_HEADER_INX-SALES_ORG = 'X'.
    GT_ORDER_HEADER_INX-DISTR_CHAN = 'X'.
    GT_ORDER_HEADER_INX-DIVISION   = 'X'.
    GT_ORDER_HEADER_INX-SALES_DIST = 'X'.
    GT_ORDER_HEADER_INX-INCOTERMS1 = 'X'.
    GT_ORDER_HEADER_INX-INCOTERMS2 = 'X'.
    GT_ORDER_HEADER_INX-PMNTTRMS =   'X'.
    GT_ORDER_HEADER_INX-PRICE_DATE = 'X'.
    GT_ORDER_HEADER_INX-PURCH_NO_C = 'X'.
    GT_ORDER_HEADER_INX-PURCH_NO_S = 'X'.
    GT_ORDER_HEADER_INX-EXCHG_RATE = 'X'.
    GT_ORDER_HEADER_INX-CURRENCY = 'X'.
*****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
    GT_ORDER_ITEMS_IN-ITM_NUMBER = '000010'.
    GT_ORDER_ITEMS_IN-MATERIAL = GT_FT_SALES-MATERIAL .
    GT_ORDER_ITEMS_IN-PO_ITM_NO = '32'.
    GT_ORDER_ITEMS_IN-CUST_MAT22 = 'AGNI-IV'.
    GT_ORDER_ITEMS_IN-BILL_DATE = '20060808'.
    GT_ORDER_ITEMS_IN-PLANT = '0001'.
*GT_ORDER_ITEMS_IN-STORE_LOC = '0001'.
    GT_ORDER_ITEMS_IN-TARGET_QTY = GT_FT_SALES-TARGET_QTY . "'1000'
    GT_ORDER_ITEMS_IN-ITEM_CATEG = GT_FT_SALES-ITEM_CATEG . "'TAN'
    GT_ORDER_ITEMS_IN-MATL_GROUP = GT_FT_SALES-MATL_GROUP . "'01'
    GT_ORDER_ITEMS_IN-PURCH_NO_C = GT_FT_SALES-PURCH_NO_C . "'32'
    GT_ORDER_ITEMS_IN-SALES_DIST = GT_FT_SALES-SALES_DIST . "'000001'
    GT_ORDER_ITEMS_IN-INCOTERMS1 = GT_FT_SALES-INCOTERMS1 . "'CFR'
    GT_ORDER_ITEMS_IN-INCOTERMS2 = GT_FT_SALES-INCOTERMS2 . "'HAMBURG'
    GT_ORDER_ITEMS_IN-PMNTTRMS = GT_FT_SALES-PMNTTRMS .    "'0001'.
    GT_ORDER_ITEMS_IN-EXCHG_RATE = GT_FT_SALES-EXCHG_RATE . "'1.00000'
    GT_ORDER_ITEMS_IN-PRICE_DATE = GT_FT_SALES-PRICE_DATE . "'20060808'
*GT_ORDER_ITEMS_IN-SALES_UNIT = 'DZ'.
    GT_ORDER_ITEMS_IN-TRG_QTY_NO = GT_FT_SALES-TRG_QTY_NO . "'23'
    GT_ORDER_ITEMS_IN-DIVISION = GT_FT_SALES-DIVISION   .   "'01'
    GT_ORDER_ITEMS_IN-SALQTYNUM = GT_FT_SALES-SALQTYNUM .   "'32'
    GT_ORDER_ITEMS_IN-GROSS_WGHT = GT_FT_SALES-GROSS_WGHT. " ' 25272000'
    GT_ORDER_ITEMS_IN-NET_WEIGHT = GT_FT_SALES-NET_WEIGHT. "'24464000'
    GT_ORDER_ITEMS_IN-UNTOF_WGHT = GT_FT_SALES-UNTOF_WGHT . " 'KG'
*GT_ORDER_ITEMS_IN-CURRENCY = 'EUR'.
    APPEND GT_ORDER_ITEMS_IN.
****<<<<<<Communication Fields: Sales and Distribution Document Item>>>
    GT_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
    GT_ORDER_ITEMS_INX-MATERIAL = 'X'.
*GT_ORDER_ITEMS_INX-PO_ITM_NO = 'X'.
    GT_ORDER_ITEMS_INX-CUST_MAT22 = 'X'.
    GT_ORDER_ITEMS_INX-BILL_DATE = 'X'.
    GT_ORDER_ITEMS_INX-PLANT = 'X'.
*GT_ORDER_ITEMS_INX-STORE_LOC = 'X'.
    GT_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
    GT_ORDER_ITEMS_INX-ITEM_CATEG = 'X'.
    GT_ORDER_ITEMS_INX-MATL_GROUP = 'X'.
    GT_ORDER_ITEMS_INX-PURCH_NO_C = 'X'.
    GT_ORDER_ITEMS_INX-SALES_DIST = 'X'.
    GT_ORDER_ITEMS_INX-INCOTERMS1 = 'X'.
    GT_ORDER_ITEMS_INX-INCOTERMS2 = 'X'.
    GT_ORDER_ITEMS_INX-PMNTTRMS = 'X'.
    GT_ORDER_ITEMS_INX-EXCHG_RATE = 'X'.
    GT_ORDER_ITEMS_INX-PRICE_DATE = 'X'.
*GT_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
    GT_ORDER_ITEMS_INX-TRG_QTY_NO = 'X'.
    GT_ORDER_ITEMS_INX-DIVISION = 'X'.
    GT_ORDER_ITEMS_INX-SALQTYNUM = 'X'.
    GT_ORDER_ITEMS_INX-GROSS_WGHT = 'X'.
    GT_ORDER_ITEMS_INX-NET_WEIGHT = 'X'.
    GT_ORDER_ITEMS_INX-UNTOF_WGHT = 'X'.
*GT_ORDER_ITEMS_IN-CURRENCY = 'x'.
    APPEND GT_ORDER_ITEMS_INX.
*****<<<<<<Communications Fields: SD Document Partner: WWW
    GT_ORDER_PARTNERS-PARTN_ROLE =   'WE'.
    GT_ORDER_PARTNERS-PARTN_NUMB = '0000000057'.
***GT_ORDER_PARTNERS-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER . " '000010'.
    APPEND GT_ORDER_PARTNERS.
*********<<<<Communications Fields: SD Document Partner: WWW>>>>>>>>>>>>>>>>>>
    GT_ORDER_SCHEDULES_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER." '000010'
    GT_ORDER_SCHEDULES_IN-REQ_QTY = GT_FT_SALES-REQ_QTY .   "'234'
    GT_ORDER_SCHEDULES_IN-DLV_DATE = GT_FT_SALES-DLV_DATE ." '20060824'.
    GT_ORDER_SCHEDULES_IN-MS_DATE = GT_FT_SALES-MS_DATE . "'20060808'
    GT_ORDER_SCHEDULES_IN-LOAD_DATE = GT_FT_SALES-LOAD_DATE. " '20060822'
    GT_ORDER_SCHEDULES_IN-GI_DATE = GT_FT_SALES-GI_DATE . " '20060823'
    GT_ORDER_SCHEDULES_IN-TP_DATE = GT_FT_SALES-TP_DATE .   "'20060821'
    APPEND gt_ORDER_SCHEDULES_IN.
*********<<<<Communications Fields: SD Document Partner: WWW FLAG>>>>>>>>>>>>>>>>>>
    GT_ORDER_SCHEDULES_INX-ITM_NUMBER = '000010'.
    GT_ORDER_SCHEDULES_INX-REQ_QTY = 'X'.
    GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-MS_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-LOAD_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-GI_DATE = 'X'.
    GT_ORDER_SCHEDULES_INX-DLV_DATE = 'X'.
    APPEND gt_ORDER_SCHEDULES_INX.
********Communication Fields for Maintaining Conditions in the Order
    GT_ORDER_CONDITIONS_IN-ITM_NUMBER = GT_FT_SALES-ITM_NUMBER ." '000010'
    APPEND GT_ORDER_CONDITIONS_IN.
***Communication Fields for Maintaining Conditions in the Order
    GT_ORDER_CONDITIONS_INX-ITM_NUMBER = '000010'.
    APPEND GT_ORDER_CONDITIONS_INX.
    CALL FUNCTION 'BAPI_SALESORDER_CREATEFROMDAT2'
      EXPORTING
   SALESDOCUMENTIN               =
        ORDER_HEADER_IN               = GT_ORDER_HEADER_IN
        ORDER_HEADER_INX              = GT_ORDER_HEADER_INX
SENDER                        =
BINARY_RELATIONSHIPTYPE       =
INT_NUMBER_ASSIGNMENT         =
BEHAVE_WHEN_ERROR             =
LOGIC_SWITCH                  =
TESTRUN                       =
CONVERT                       = ' '
     IMPORTING
       SALESDOCUMENT                  = GT_SALESDOCUMENT
      TABLES
       RETURN                         = GT_RETURN
        ORDER_ITEMS_IN                = GT_ORDER_ITEMS_IN
        ORDER_ITEMS_INX               = GT_ORDER_ITEMS_INX
        ORDER_PARTNERS                = GT_ORDER_PARTNERS
       ORDER_SCHEDULES_IN            = GT_ORDER_SCHEDULES_IN
       ORDER_SCHEDULES_INX           = GT_ORDER_SCHEDULES_INX
       ORDER_CONDITIONS_IN           = GT_ORDER_CONDITIONS_IN
       ORDER_CONDITIONS_INX          = GT_ORDER_CONDITIONS_INX
ORDER_CFGS_REF                =
ORDER_CFGS_INST               =
ORDER_CFGS_PART_OF            =
ORDER_CFGS_VALUE              =
ORDER_CFGS_BLOB               =
ORDER_CFGS_VK                 =
ORDER_CFGS_REFINST            =
ORDER_CCARD                   =
ORDER_TEXT                    =
ORDER_KEYS                    =
EXTENSIONIN                   =
PARTNERADDRESSES              =
    IF GT_RETURN-TYPE EQ 'E' .
      E_REC = E_REC + 1.
      READ TABLE GT_RETURN WITH KEY ID = 'V1'.
      FORMAT COLOR COL_NEGATIVE INVERSE ON.
      REC_NO = E_REC + S_REC.
          CONCATENATE TEXT-006 REC_NO ':'
          GT_RETURN-MESSAGE INTO MSG SEPARATED BY SPACE .
          CONDENSE MSG.
          WRITE: / MSG.
      FORMAT COLOR COL_NEGATIVE INVERSE OFF.
ELSEIF GT_RETURN-TYPE EQ 'S'.
      S_REC = S_REC + 1.
      FORMAT COLOR COL_POSITIVE INVERSE ON.
          MSG = GT_RETURN-MESSAGE.
          CONDENSE MSG.
          WRITE: / MSG .
      FORMAT COLOR COL_POSITIVE INVERSE OFF.
     PERFORM COMMIT_MM.
ENDIF.
      CLEAR: GT_RETURN[], MSG.
ENDFORM.                    " SLALE_UPLOAD_DATA
*&      Form COMMIT_MM
      text
--> p1        text
<-- p2        text
FORM COMMIT_MM .
CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
      EXPORTING
        WAIT   = 'X'
      IMPORTING
        RETURN = GT_RETURN.
clear:      GT_ORDER_ITEMS_IN[],GT_ORDER_CONDITIONS_IN[].
ENDFORM.                    " COMMIT_MM

How to create excise invoice with refer to Delivery Note

Hi SAP Expert,
I am doing STOCK Transport process from factory to depot and hitting error while creating excise invoice in Factory.
From SAP help on Creating Excise Invoice, it said :
From the SAP Easy Access screen, choose Indirect Taxes ® Sales/Outbound Movements ® Excise Invoice ® For Sales Order ® Outgoing Excise Invoice Create/Change/Display ®
If you want to create the excise invoice with reference to a pro forma excise invoice or commercial invoice, choose Excise Invoice ® Create.
If you want to create the excise invoice with reference to a delivery note, choose Exc. inv. for delivery ® Create.
Enter the number of the reference document.
- When i created the excise invoice with reference to a STO Delivery Note, i am getting error : " For delivery 800050092 no document of type JEX exist "
- I already setup the config to assign Delivery Type NL to billing type JEXP.
I was doing the steps as below :
1. ME21N u2013 Create Stock Transport Order
2. VL10B u2013 Create Outbound Delivery w.r.t. STO
3. J1IIN u2013 Create Outgoing Excise Invoice w.r.t. Delivery Note
- Anything that i am missing ?

Hi Guru,
Thanks for your reply. It is my typo error. I have maintained the delivery type NL to billing type JEX, instead of JEXP
I am getting error :
For delivery 800050092 no document of type JEX exist
Message no. 8I320
Diagnosis
The excise reference document defined does not exist for the delivery.
Procedure
Create the excise reference document before running the excise posting transaction.
- What is it means by create the excise reference document before running the excise posting transaction ? Do I need to create Pro-forma invoice prior to execute transaction J1IIN ?
I did not check the selection for ": Excise Inv during Billing " in my Excise Group maintainance.

WBS element to remain when creating a quotation with ref

Hi ,
I have a requirement , when a quotation is created with reference to another quotation the a new WBS element should not be created instead it has to be the same as the one of the reference quotation . Is there any exit or routine where i can code this ?
Thanks .
Priya.

Did you solve this issue?

Delivery Created for material with ref to a sales Order, even if the stock

Hi Guru,
Deliveriey is getting created of material having TANN as Item category in the sales Order. We want the system to stop creating a delivery, when there is no stock of the same.
How can we configure the scenario.
Please help.
Regards
Amit Shrivastava

Hi amit
If you feel this answer solve your query please reward with points.
With out stock also you can create a delivery and picking you will get delviery doucment number But the thing is when you cannot do the post goods issue
Deficit of SL Unrestricted-use you will get this type of messege when you do the p..g.i. Post goods issue is the thing it will update the inventory. There is no stock it will not update any stock temparay it will create all those things.
Thanks & Regards
rack29

Create Sales Order with ref to PO

hello experts ,
is it possible to create a sales order wrt a PO?
Regds
Anis

hi,
Yes you can create from VA01...enter order type and then click on the "create with reference"...here see the tab order...enter the PO number and execute...
Hope it helps..
Regards
Priyanka.P

Is it possible to create a role with PERM_READER_EXTENSIONS_WEB_APPLICATIONS without Service Invoke?

I need to restrict user access to Workspace processes. Using the adminui, service management, I gave my test group INVOKE_PERM permissions to this service. This works good. The users of the test group can only see this process. However, for these users the SOAP calls do not work. I am using a reader extended form and I am getting the error below. If I add the Reader Extension Web Application role, the SOAP call work, but the user of the test group can see all other processes. I created a role and gave it PERM_READER_EXTENSIONS_WEB_APPLICATIONS, Service Read, INVOKE_PERM and other combinations. This role only works if I add Service Invoke and this give users access to all processes. How can I get a role to provide the Reader Extension without using Service Invoke?
An error has occurred. See error log for more details.
User TORRES, ALEJANDRO G does not have the Service Invoke Permission on Service ReaderExtensionsService.

I found the answer to my question. I had to give INVOKE permission to all the services used by the process.

Partner function not working when creating PO with ref to PReq

Partner function is not working when creating a Purchase Order with ref to a Purchase Requistion, Partner functions maintained in the vendor master are VN, OA & PI.
But OA & PI are not appearing in the PO header partner tab when created with ref to PR.
however it works when i create the PO directly ( without the PR ref )
I am using the same material & Plant for both manual PO & PR to PO.
Any idea what could be wrong .
I have maintained the settings for schema groups for vendor master & purchasing doc in the partner determination.
Thanks
Dkmurthy

Hi,
I have also an issue that seems similar to one you are discussing.
When we use ME59N and create a PO with ref. from a PR (created from a sales order), the message determination works well, it reads the condition set in MN04 (condition records for messages), and creates a message (with output type for EDI , medium: 6, and partner function LS: Logical system). Message is created and idoc is sent.
When we try with ME21N, ME21 and we create the PO with ref. to the same PR, either by entering manually the PR in the document overview of ME21N or by selecting the PR (without entering the PR number), i.e with date, the message is not created in the PO.
Company code is assigned to purchase organization, and so is purchase organization to plant.
Any idea why there is no automatic message determination in the case of the transaction: ME21N
Note: If I try ME21N, and enter the output type and partner, manually, I receive a warning message
VN006 (Partner XXXX does not exist for partner function LS). If I accept this warning message, then message is saved- idoc is sent. However I can not overcome the warning message, if it plays any role, because I can not assign partner function LS to the vendor.Then I receive message CZ 327 (Can not use this partner role).
Any input is wellcome.

How to create Invoice with ref to PO

Dear sd gurus..
i know we can create invoice with ref to sales order not with po
But i want to create Invoice with ref to po only
please guide me
Thanks a lot

Venu, thanks for your reply.
So in this case your idea wont work but the main imp thing is we cant create invoice with ref to po
Please read my post once again, i never said we can create customer invoice with ref to Purchase order. I said very clearly, " you can follow the normal 3rd party sales process", which means we create customer invoice with ref to sales order only.
Coming into another query,
but some time PO Is generated 110 qth to vendor but vendor may be he will send 105 due to shortage ... and he will tell i will send the the remaining stock after next 10 days now Generally miro will happen only for 105 not 110 ( even we can do MIRO110 also ) but i am talking generally because he received the stock 105 only
But company wants billing for 110 not for 105 because here customer accepted to pay full money
and vendor gave promise to delivery 5 qty in next 10 days
Why will the customer agree to be billed the full qty, when he receive the partial qty?
Let us assume as you said customer agree to pay for full qty, then there are two options.
1. Do the MIRO for full qty since you would be invoicing the customer for full qty
Or
2. Do the MIRO for partial qty and customer should agree for partial invoice
Please note in the normal case also if there is if condition then you don't have other option.
Example:
Order = 100 qty
PO = 100 qty
MIGO = 50 qty and remaining 50 qty Vendor delivery in next 10 days
MIRO =50 qty
But here also customer agreed to pay for full qty, then what will you do ? you don't have other option but to bill the partial qty in standard.
And let me know if you need any more clarity?
thanks,
Srinu.

Restriction of creating p.o with refe. to service P.R

Similar Messages

Maybe you are looking for