Infotype for maintaining sal in usd

hi gurus,
i have got a recquirement
my organisation  wants to maintain the some employess  basic pay details in us $ .
how to maintain that .
pls help me.

Hi,
First of all please maintain curriencies and you have a field in IT 0008 Payment currency here you can maibntauin different currency and in IT 0009 currency field is there.
Regards,
Kapil

Similar Messages

  • Maintaining sales enquiry

    what are the essential steps for maintaining sales inquiry. i use T.C - VA11, after filing all details it flashes a error regarding access sequence. what i do now, please suggest................
    thanks in advance

    Hi Kumar,
    The fields are to chosen as per your client's requirement.
    Go to Display Condition Tables (v/05) & put the table number which you want to maintain & enter.You will get the fields on LHS for which you have to maintain the Condition Records for automatic determination of pricing.
    Put these condition tables in the Access Sequence.
    Regards,
    Hemant Patil

  • Bapi for creating Sales Area data on Relationship

    Hi,
    I am looking for BAPI for creating relationship between business partners with sales area data in CRM 5.0.
    Example - I would like to create relationship type CRMH03.
    Bapi BUPR_RELATIONSHIP_CREATE does not allow for maintaining sales area data (Sales org, distribution channel, division).
    Does anybody know such a bapi?
    Regards
    Radek

    hi
    try using these
    BAPI_BUPA_CREATE_FROM_DATA
    BAPI_BUPA_RELATIONSHIP_CREATE
    best regards
    ashish

  • BAPI for uploading sales order

    Hi Guys,
                 I have upload the sales order data from a flat file to SAP system using BAPI, can you please tell step by step process how to do that. My flat file contains the following contents with the fields : Order type, sales organization,dist channel, divison, PO no., SP,SH , material no. , quantity and price.
    OR     1000     12     00     DG-20010112-4     2004     2004     M-16     40     1000
    OR     1000     12     00     DG-20010112-4     2004     2004     M-12     20     2000
    OR     1000     10     00     12134     1032     1032     m-12     35     2000
    thanks
    rajeev Gupta

    see this example program
    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

  • What are the infotypes required for maintaining benefits....

    Hi
    Please help ...
    What are the ingotypes required for maintaing benefits....

    Hi Srikanth,
    Please find below the list of Infotypes required for maintaining benefits:
    1. General Benefits Information (Infotype 0171)
    2. Adjustment Reasons (Infotype 0378)   
    3. Health Plans (Infotype 0167)  
    4. Insurance Plans (Infotype 0168)  
    5. Savings Plans (Infotype 0169)  
    6. Flexible Spending Account (Infotype 0170)  
    7. Miscellaneous Plans (Infotype 0377)  
    8. Family/Related Person (Infotype 0021)
    There are also other benefits infotypes e.g. Stock Purchase Plans (Infotype 0379), Credit Plans (Infotype 0236) and many COBRA and retirement plan infotypes but these are used based on the company requirement.
    I hope this helps.
    Regards,
    Anand Jalan
    Edited by: Anand Jalan on Jan 6, 2010 9:50 PM
    Edited by: Anand Jalan on Jan 6, 2010 9:52 PM

  • FM/BAPI/CLASS for  VA01,VA02,VA03 ie maintain sales order.

    Hi,
       Is there any FM or Class to maintain sales orders. Any help will be appriciated.
    Regards,
    Sami.

    Go to SE37 and search for BAPISALESORDER*
    You find a list of bapi's. Some examples:
    BAPI_SALESORDER_CHANGE
    BAPI_SALESORDER_CONFIRMDELVRY
    BAPI_SALESORDER_CREATEFROMDAT1
    BAPI_SALESORDER_CREATEFROMDAT2
    BAPI_SALESORDER_CREATEFROMDATA
    BAPI_SALESORDER_GETLIST
    BAPI_SALESORDER_GETSTATUS
    BAPI_SALESORDER_SIMULATE
    I checked and didn't found a class for this but i guess the one you want is BAPI_SALESORDER_CHANGE.
    The BAPI does not do a commit therefor use the following after the first BAPI: BAPI_TRANSACTION_COMMIT
    Edited by: Christophe Gillijns on May 26, 2010 3:27 PM

  • Credit Block for released sales order

    Dear All,
    I have got one issue. There is a sales order which was created earlier say 15 days back. It went into the credit block at the time of saving it. It was released through VKM3 too.
    Now when i change any field in the sales order today, it is going into the credit block. We are not changing any value of any of the item. Just maintaining the Billing block in it or remobving the Billing block.
    The number of days maintained in the OVA8 are 182. So as per the standard functionality it should not go into the credit block for any change in the sales order like changing the billling date or changing the billing block.
    Can you please let me know what might be the reason for this sales order to go into the credit block..??? Any help is very much appreciated.
    Thanks and regards,
    Vishi.

    Dear Vishi
    Please check if you have checked the critical fields option.
    Credit check against critical fields (fixed value dates)
    The indicator controls the critical field check. If the field is selected, the system checks whether critical fields have been changed.
    Use
    If a check is carried out, the following fields are relevant:
    Payment terms
    Additional value days
    Fixed value date
    Note
    Use this type of check for sales documents only.

  • Creation of Excise Invoice for Sample Sales

    Hi Gurus,
    When i create excise invoice for sample sales against the invoice the excise duties are not capturing it is showing as zero value. Can you give suggestions to solve this.
    Regards
    Kiran

    If the excise values flowing in billing document but not in excise document, then you need to check in the following IMG
    Logistics-General --> Tax on Goods Movements --> India --> Account Determination.
    There you have to maintain the respective G/L accounts for excise and also in the next tab you have to specify the G/L Accounts per Excise Transaction.
    For information, for outgoing excise invoice, the excise transaction type would be DLFC.
    thanks
    G. Lakshmipathi

  • TANN item category item not picking for return sales order

    Hi all,
    I have a question regarding TANN item category. This TANN item category item is not picking for return sales order type. As far as i know RENN is the free goods for return sales order. Can you please clarify the above question further

    Hi
    If you are making return order by copying sales order then please see this procedure also.
    Try to check in the copy control also.
    Go to the following path IMG u2013 Sales and Distribution u2013 Sales u2013 Maintain Copy control for sales documents. (Tcode VTAA)
    Select copying control : sales document to sales document.
    Search your return delivery order from the reference sales document type.
    Then select the item from the left side Colum.
    Go and find out TANN item category and click on detail.
    Check out Item Cat proposal. If it is empty then type your RENN condition type over here.
    Now try to create the return sales order it might work.
    Raj.

  • Creation of RG1 for Export Sales

    Hi,
    Frends,
    For Export Sales Customer wants to create RG1, but i dont know how to create that can u pl send me some tips of creation of RG1.
    Thanks and Regards
    Babu Rao

    Hi Babu Rao,
    RG1 register is a register of Daily stock account. Whatever stcock you produce n move to warehouse specifically for excisable finished goods, RG1 captures all these movements of material to your warehouse/store. And thr is standard program given in by SAP to create RG1. Mostly, u dont need to create a Z report for that.
    Rg1 consists of fields like
    for matl XXX   -
    closing bal(quantity till last day); 
    quantity mfged today;
    total quantity;
    excise duty payable on them etc
    By T code J1iex u will be able to create the RG1 or some other registers. then update the entries in the registers(then registers will show new data)
    update registers- j1i5
    extract data- j2i5
    print register- j216
    in this sequence only. because this is the procedure for maintaining any register. In each code, u will find selection criteria, n need to choose register that u intend to maintain.
    If u need to create RG1 specifically for exports' use tables :
    vbrp, vbrk, konv, kna1
    j_1iexchdr (excise header), j_1iexdtl(excise item), j_1imtchid(for matl chapter id)
    from j_1iexdtl(excise item), u can find tables of excise values.
    from vbrp, fetch the document no., matl number
    hope this will help you.
    Reward, if it helps.
    Prashant

  • VPRS Cost not pickibng only for single sales order

    Hello Gurus
    Goodevening every body
    If we maintain  two prices  in material master one is moving average and another  one  is stanrdard price which  price the system will pick in the  sales order of my pricing procedure.
    Note-Only for one sales order system is not picking  VPRS  cost in my sales when was doing testing and giving some  message  in condition analysis -VPRS     111 Condition ignored (requirement 004 not fulfilled)
    I tried to analysis it but not able to come final conclusion this  message
    I am looking for your inputs
    Thanks in advance
    Regards
    Venkat

    Something wrong in the "item category" settings for that material.
    Pls activate "determine cost" control in the item category setting.
    Revert back for confirmation.
    Rgds
    Sumanth.Gururaj
    Consultant/Systems Analyst - SAP SD/MM

  • Error in Creating Excise Invoice for Factory Sale

    Dear Friends:
    Using T.code J1IIN ( Create Excise invoice for Factory Sale), I entered data for billing doc,posting date,sub transaction type & pressed enter and tried to save it.I got the error 'Error in allocating internal document number interval not found number object J_1IINTNUM'.
    Using T.code J1I9, I used the number object J_1IINTNUM and created number ranges and again tried to save T.code J1IIN ( Create Excise invoice for Factory Sale), but still i am getting the same error.
    Please let me know how to solve the error. This will be highly Appreciated.
    Srinu NV

    Hi,
    In Excise Invoice, there is always an internal number range which is required to be maintained. This is maintained through Transaction Code: SNRO & object being J_1IINTNUM . As soon as you maintain the same, it will resolve the error.
    I learned the above by commiting a same mistake in one of the project.
    Regards,
    Rajesh Banka
    Reward points if helpful.

  • OV77 Assign g/l account for cash sale only

    Dear FI Experts very good mng
    i am sd consuultant I know VKOA Account determination Process but OV77 Also Assign G/L Account For cash sales only
    i thing For cash sale also we can maintaine Account Determination proceduere we can use VKOA But i want to know any special thing is there For OVKK ?
    Thanks a lot
    Plz forgive me if it is basic question

    Hi,
    Please check whether below thread is useful to you
    Cash Sales Process & Accounting Entries
    Regards,
    Tejas

  • Want to change output type for 10000 sales orders through MASS

    Hi Friends,
    I would like to change the Output type in the sales order for 10000 sales orders.
    Can I do with MASS transaction. If so, Plz let me know how ?
    Is there any other process to change the output type for 10000 sales orders, as its difficult to manually in each and every sales order.
    Its very urgent issue, Plz let me know at the earliest.
    Thanks & Regards,
    Praveen Kumar. A

    This may be little tough for 10000 sales orders.
    1. You have to remove the output record for the irrelevant output record using tcode VV12 for the relevant document type. So now for the document type, the old output wont be triggered.
    2. Now, create output records for hte correct output type in VV11 tcode(for the output type BA03) for the document type. Now this output will be triggered for all the document types you are creating from now onwards.
    3. To trigger the output type BA03, in all the old orders, you just have to open these sales orders in change mode (VA02), and just save it. When u open it the output type BA03 will be automatically triggered as the master data is maintained in VV11. But because just opening all the 10000 sales orders in VA02 one by one be a mechanical task, you have to think of some tool for this.
    May be a CATT procedure can do the trick. Else, you can just create a small program, where you can upload these sales orders and the program will just open these orders in change mode and just saves it (without making any changes). Then the output will be retriggered.
    Here again, if you are printing the output directly, it is advisable to trigger the output in batch mode(Date/Time field is 1 in VV11), and then you can again trigger the printing again using the program RSNAST00 after office hours for these 10k orders.
    I hope I answered ur query.
    Pls lemme know if you need some more info. (You can reward me too...)

  • Infotype for Personnel Email Address

    Hi,
    What is the Infotype to maintain the Personnel Email Address? I have an Interface Updating Employee Vendor Master Records from the HR Master Records but it is not updating the Email Address. Can you please suggest me what should be done to make this working? Is there any configuration to be done?
    Appreciate your Help!
    Thanks,
    Kannan.

    Standard SAP programs look for the value in the field USRID_LONG of subtype 0010 of Infotype 0105. It is suggested to use this subtype to mainatin emplyee's email id.
    Arya

Maybe you are looking for