How to validate the line item values in OFR - quantity , unit price and UOM

Hi All,
Is there any possibility to validate the line items like quantity, unit price and UOM against the DB and stops those invoices at verifier (1 batch =10 invoices) level  if yes could you please let me know the process how to proceed further.
due to this some the invoices are coming to OFR is with incorrect quantity, UOM and unit price different from PO lines information like quantity , UOM and unit price and those invoices are not validating from the DB and these are processed to EBS and it's effecting the GL and reporting.
Regards,
Anil

Hi ,
I did not get the exact requirement.Let me bit:
In standard AP project lines validation will try to compare the quantity , unit price and UOM of line against the database for match which actually performed on export.
So even if match fails batch will be exported.Now if you want to correct it before EBS,i think you can do it in the business process easily that you are consuming whether BPEL/BPM process.
We have done this in several projects
=========================
But If you want that to be done from OFR side i think we need to code  UserExitPONumberValidate event to  compare the line items values against database.I need to test this also.

Similar Messages

  • How to combine the line items of 2 Sales orders into 1 delivry

    how to combine the line items of 2 Sales orders into 1 delivry
    and their process, pre-requisites and tcode

    The prerequisites are:
    1) In the customer master sales area data, shipping tab, there is a field called Order combination. u must tick that.
    2) for the two orders, the sold to party & ship to party must be same
    3) both orders must have created from same plant & shipping points
    4) the line items must have same loading grp.
    5) the both orders sheduline line date must be same.
    transaction code for the same is VL04.
    enter the required data and select the order nos to be processed.
    Do reward points if it is useful

  • How to clear the line items once posted...

    hello experts,
    i m workiing on Enhancements in fi/co...i m not able to get the actual exit..
    How to clear the line items once postings has been done...i.e. once v do postings in f-48 v assign an assignment with special GL a/c as 'A'(one line item generates)....and in Tr.code f-43 once the due as been settled i.e the payment as been done and same assignment has to be given(2nd line item generates) it has to clear with the transaction f.13.but it is not..there is a report program to check fbl1n(tr.code)...once it is cleared it is shown in cleared items else it is shown in open items.....can any one help me out...
    i m providing the tech names of the fields...
    same program for both the transactions-- sapmf05a screen no for f-48--304 and
    f-43 ---110....
    Assignment --- BSEG-ZUONR....AMOUNT ---(cluster table) BSEG-WRBTR....
    SPECIAL GL A/C RF05A-UMSKZ(structure)
    thanks n regards,
    vamshi

    The prerequisites are:
    1) In the customer master sales area data, shipping tab, there is a field called Order combination. u must tick that.
    2) for the two orders, the sold to party & ship to party must be same
    3) both orders must have created from same plant & shipping points
    4) the line items must have same loading grp.
    5) the both orders sheduline line date must be same.
    transaction code for the same is VL04.
    enter the required data and select the order nos to be processed.
    Do reward points if it is useful

  • How to change the line item storage location during the sales order creatio

    How to change the line item storage location during the sales order creatio

    Hi Kumar,
    I think you can just delete it in the sales order directly, if you are using make-to-order scenario, then there will be special stock left for the sales order as the production has been goods receipt, you need to use MM transaction move the stock to unrestricted use stock. If you are using make-to-stock scenario, there should be no further problem. If you are using assembly order, please try to reject the sales order item to see if it could fullfill your requirement.
    Regards,
    Rachel

  • How to increase the line items against the std no of line items in MIGO

    hi,
    I have PO with more than 100 line items
    During GR system is showing the error message as
    Maximum number of items F1 reached
    What is the standard no of line items in MIGO
    And how to increase the line items
    Is there any notes to apply
    plz give sutable solution
    K.Raghuram

    Do you get message F5727 "Maximum number of items in FI reached"? reason is that in FI the posting line has a three-digit line item number (BSEG-BUZEI).
    SAP's note 117708 provides a modification. I am pasting solution below.
    Via the summarization you can post documents with more than 999 items in
    FI.
    The modification required for this is small, in addition you have to
    change 2 tables. The modification is carried out in FI not in invoice
    verification.
    To activate document summarization in FI proceed as follows:
    - The changes are described in Note 36353 and for the
    modification in Note 77161. You may also have to apply Note
    67640 so that the document summarization affects inventory
    management.
    An advice for the notes:
    36353: Solution point 3: Field name WERKS
    77161: Solution point 2: Maintain table TTYPV with Transaction
    SE16
    - this has the following effects; you can no longer clear the
    GR/IR clearing account on purchase order item level (but only
    on purchase order level) and you can only display the FI data
    summarized (also see Note 36353)

  • How to delete the line item from a sales order

    Hi all,
    how to delete a line item from the sales order for which the production is already happened and it has been delivered. the production order status is DLV.
    Regards
    Kumar

    Hi Kumar,
    I think you can just delete it in the sales order directly, if you are using make-to-order scenario, then there will be special stock left for the sales order as the production has been goods receipt, you need to use MM transaction move the stock to unrestricted use stock. If you are using make-to-stock scenario, there should be no further problem. If you are using assembly order, please try to reject the sales order item to see if it could fullfill your requirement.
    Regards,
    Rachel

  • How to add the line item text in the Ledger line item report

    Hi SAP Gurus,
    I having one requirement from the user. He wants the line item text which we will enter in FB60/FB70/FB50 has to be shown in the Ledger line item report. Right now this field is not available. Is there any possible we can make this line item text in the ledger line item report i.e. FBL1N/FBL3N/FBL5N?
    advance thanks for the help.
    Regards,
    Deva.

    Hi,
    You can do the below to get this. (You can change the names of the function modules as per your wish/ organization naming convention):-
    Step 1:-
    Create function module Z_GET_SGTXT as below:-
    Import:-
    BELNR LIKE BKPF-BELNR
    BUKRS LIKE BKPF-BUKRS
    BUZEI LIKE BSEG-BUZEI
    GJAHR LIKE BKPF-GJAHR
    Export:-
    PRCTR LIKE BSEG-SGTXT
    FUNCTION Z_GET_SGTXT.
    ""Local Interface:
    *" IMPORTING
    *" VALUE(BELNR) LIKE BKPF-BELNR
    *" VALUE(BUKRS) LIKE BKPF-BUKRS
    *" VALUE(BUZEI) LIKE BSEG-BUZEI
    *" VALUE(GJAHR) LIKE BKPF-GJAHR
    *" EXPORTING
    *" VALUE(SGTXT) LIKE BSEG-SGTXT
    SELECT SINGLE SGTXT FROM BSEG INTO SGTXT WHERE GJAHR = GJAHR
    AND BELNR = BELNR
    AND BUKRS = BUKRS
    AND BUZEI = BUZEI.
    ENDFUNCTION.
    Step 2:-
    Then create the Function Modules as below:-
    Z_LINE_ITEMS_GET_SGTXT (Copy of SAMPLE_INTERFACE_00001650)
    FUNCTION Module Z_LINE_ITEMS_GET_SGTXT.
    ""Local Interface:
    *" IMPORTING
    *" VALUE(I_POSTAB) LIKE RFPOS STRUCTURE RFPOS
    *" EXPORTING
    *" VALUE(E_POSTAB) LIKE RFPOS STRUCTURE RFPOS
    Initialize Output by using the following line
    E_POSTAB = I_POSTAB.
    E_POSTAB = I_POSTAB. "<-- important
    CALL FUNCTION 'Z_GET_SGTXT'
    EXPORTING
    BELNR = I_POSTAB-BELNR
    BUKRS = I_POSTAB-BUKRS
    BUZEI = I_POSTAB-BUZEI
    GJAHR = I_POSTAB-GJAHR
    IMPORTING
    SGTXT = E_POSTAB-SGTXT
    EXCEPTIONS
    OTHERS = 1.
    ENDFUNCTION.
    Step3:-
    Transaction FIBF:-
    Settings -> Products -> of a Customer
    SGTXT Text in Line Item Display Active
    Settings -> P/S Module -> of a Customer
    00001650 SGTXT Z_LINE_ITEMS_GET_SGTXT
    Step 4:-
    Create the layout for FBL*N with display of the TEXT.
    Regards,
    Gaurav

  • How to add the line items while running the VA01

    HI All,
    I want to add the line items while I am running the VA01 t-code(In run time).Could anybody give the FM to create the line items....Its urgent

    Hi ,
    User Exits In Sales Document Processing
    This IMG step describes additional installation-specific processing in sales document processing. In particular, the required INCLUDES and user exits are described.
    Involved program components
    System modifications for sales document processing affect different areas. Depending on the modification, you make the changes in the program components provided:
    MV45ATZZ
    For entering metadata for sales document processing. User-specific metadata must start with "ZZ".
    MV45AOZZ
    For entering additional installation-specific modules for sales document processing which are called up by the screen and run under PBO (Process Before Output) prior to output of the screen. The modules must start with "ZZ".
    MV45AIZZ
    For entering additional installation-specific modules for sales document processing. These are called up by the screen and run under PAI (Process After Input) after data input (for example, data validation). The modules must start with "ZZ".
    MV45AFZZ and MV45EFZ1
    For entering installation-specific FORM routines and for using user exits, which may be required and can be used if necessary. These program components are called up by the modules in MV45AOZZ or MV45AIZZ.
    User exits in the program MV45AFZZ
    The user exits which you can use for modifications in sales document processing are listed below.
    USEREXIT_DELETE_DOCUMENT
    This user exit can be used for deleting data which was stored in a separate table during sales document creation, for example, if the sales document is deleted.
    For example, if an additional table is filled with the name of the person in charge (ERNAM) during order entry, this data can also be deleted after the sales order has been deleted.
    The user exit is called up at the end of the FORM routine BELEG_LOESCHEN shortly before the routine BELEG_SICHERN.
    USEREXIT_FIELD_MODIFICATION
    This user exit can be used to modify the attributes of the screen fields.
    To do this, the screen fields are allocated to so-called modification groups 1 - 4 and can be edited together during a modification in ABAP. If a field has no field name, it cannot be allocated to a group.
    The usage of the field groups (modification group 1-4) is as follows:
    Modification group 1: Automatic modification with transaction MFAW
    Modification group 2: It contains 'LOO' for step loop fields
    Modification group 3: For modifications which depend on check tables or on other fixed information
    Modification group 4: is not used
    The FORM routine is called up for every field of a screen. If you require changes to be made, you must make them in this user exit.
    This FORM routine is called up by the module FELDAUSWAHL.
    See the Screen Painter manual for further information on structuring the interface.
    USEREXIT_MOVE_FIELD_TO_VBAK
    Use this user exit to assign values to new fields at sales document header level. It is described in the section "Transfer of the customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAK_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBAP
    Use this user exit to assign values to new fields at sales document item level. It is described in the section "Copy customer master fields into the sales document".
    The user exit is called up at the end of the FORM routine VBAP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBEP
    Use this user exit to assign values to new fields at the level of the sales document schedule lines.
    The user exit is called up at the end of the FORM routine VBEP_FUELLEN.
    USEREXIT_MOVE_FIELD_TO_VBKD
    Use this user exit to assign values to new fields for business data of the sales document. It is described in the section "Copy customer master fields into sales document".
    The user exit is called up at the end of the FORM routine VBKD_FUELLEN.
    USEREXIT_NUMBER_RANGE
    Use this user exit to define the number ranges for internal document number assignment depending on the required fields. For example, if you want to define the number range depending on the sales organization (VKORG) or on the selling company (VKBUR), use this user exit.
    The user exit is called up in the FORM routine BELEG_SICHERN.
    USEREXIT_PRICING_PREPARE_TKOMK
    Use this user exit if you want to include and assign a value to an additional header field in the communication structure KOMK taken as a basis for pricing.
    USEREXIT_PRICING_PREPARE_TKOMP
    Use this user exit if you want to include or assign a value to an additional item field in the communication structure KOMP taken as a basis for pricing.
    USEREXIT_READ_DOCUMENT
    You use this user exit if further additional tables are to be read when importing TA01 or TA02.
    The user exit is called up at the end of the FORM routine BELEG_LESEN.
    USEREXIT_SAVE_DOCUMENT
    Use this user exit to fill user-specific statistics update tables.
    The user exit is called up by the FORM routine BELEG-SICHERN before the COMMIT command.
    Note
    If a standard field is changed, the field r185d-dataloss is set to X. The system queries this indicator at the beginning of the safety routine. This is why this indicator must also be set during the maintenance of user-specific tables that are also to be saved.
    USEREXIT_SAVE_DOCUMENT_PREPARE
    Use this user exit to make certain changes or checks immediately before saving a document. It is the last possibility for changing or checking a document before posting.
    The user exit is carried out at the beginning of the FORM routine BELEG_SICHERN.
    User exits in the program MV45AFZA
    USEREXIT_MOVE_FIELD_TO_KOMKD
    Use this user exit to include or assign values to additional header fields in the communication structure KOMKD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMPD
    Use this user exit to include or assign values to additional item fields in the communication structure KOMPD taken as a basis for the material determination. This is described in detail in the section "New fields for material determination".
    USEREXIT_MOVE_FIELD_TO_KOMKG
    Use this user exit to include or assign values to additional fields in the communication structure KOMKG taken as a basis for material determination and material listing. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_MOVE_FIELD_TO_KOMPG
    Use this user exit to include or assign values to additional fields in the communication structure KOMPG taken as a basis for material determination and material listung. This is described in detail in the section "New fields for listing/exclusion".
    USEREXIT_REFRESH_DOCUMENT
    With this user exit, you can reset certain customer-specific fields as soon as processing of a sales document is finished and before the following document is edited.
    For example, if the credit limit of the sold-to party is read during document processing, in each case it must be reset again before processing the next document so that the credit limit is not used for the sold-to party of the following document.
    The user exit is executed when a document is saved if you leave the processing of a document with F3 or F15.
    The user exit is called up at the end of the FORM routine BELEG_INITIALISIEREN.
    User-Exits in program MV45AFZB
    USEREXIT_CHECK_XVBAP_FOR_DELET
    In this user exit, you can enter additional data for deletion of an item. If the criteria are met, the item is not deleted (unlike in the standard system).
    USEREXIT_CHECK_XVBEP_FOR_DELET
    In this user exit, you can enter additional data for deletion of a schedule line. If the criteria are met, the schedule line is not deleted (unlike in the standard system).
    USEREXIT_CHECK_VBAK
    This user exit can be used to carry out additional checks (e.g. for completion) in the document header. The system could, for example, check whether certain shipping conditions are allowed for a particular customer group.
    USEREXIT_CHECK_VBAP
    This user exit can be used to carry out additional checks (e.g. for completion) at item level.
    USEREXIT_CHECK_VBKD
    The user exit can be used to carry out additional checks (e.g. for completion) on the business data in the order.
    USEREXIT_CHECK_VBEP
    This user exit can be use to carry out additional checks (e.g. for completion) on the schedule line. During BOM explosion, for example, you may want certain fields to be copied from the main item to the sub-items (as for billing block in the standard system).
    USEREXIT_CHECK_VBSN
    You can use this user exit to carry out additional checks (e.g. for completion) on the serial number.
    USEREXIT_CHECK_XVBSN_FOR_DELET In this user exit, you can enter additional criteria for deletion of the serial number. If the criteria are met, the serial number is not deleted (unlike in the standard system).
    USEREXIT_FILL_VBAP_FROM_HVBAP
    You can use this user exit to fill additional fields in the sub-item with data from the main item.
    USEREXIT_MOVE_FIELD_TO_TVCOM_H
    You can use this user exit to influence text determination for header texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    USEREXIT_MOVE_FIELD_TO_TVCOM_I
    You can use this user exit to influence text determination for item texts. For example, you can include new fields for text determination or fill fields that already exist with a new value.
    User-Exits for product allocation:
    The following user exits all apply to structure COBL, in which the data for account determination is copied to item level.
    USEREXIT_MOVE_FIELD_TO_COBL
    Option to include new fields in structure COBL.
    USEREXIT_COBL_RECEIVE_VBAK
    Option to assign values from the document header to the new fields.
    USEREXIT_COBL_RECEIVE_VBAP
    Option to supply values from the item to the new fields.
    USEREXIT_COBL_SEND_ITEM
    A changed field can be copied from the structure into the item. You could use the user exit to display a certain field in the account assignment block (see also MV45AFZB).
    USEREXIT_COBL_SEND_HEADER
    A changed field can be copied from the structure to the header (see source text MV45AFZB)
    USEREXIT_SOURCE_DETERMINATION
    You can use this user exit to determine which plant will be used for the delivery. In the standard system, the delivering plant is copied from the customer master or the customer-material info record. If you want to use a different rule, then you must enter it in this user exit.
    USEREXIT_MOVE_FIELD_TO_ME_REQ
    With this user exit you can include additional fields for the following fields:
    EBAN (purchase requisition)
    EBKN (purchase requisition-account assignment)
    USEREXIT_GET_FIELD_FROM_SDCOM
    Option to include new fields for the variant configuration. Fields that are included in structure SDCOM can be processed and then returned to the order.
    USEREXIT_MOVE_WORKAREA_TO_SDWA
    You can use this user exit to format additional work areas for the variant configuration. You will find notes on the user exit in MV45AFZB.
    User-Exits for first data transfer:
    The following user exits can only be used for the first data transfer.
    Note
    Only use the user exits if the names/fields do NOT have the same name.
    USEREXIT_MOVE_FIELD_TO_VBAKKOM
    Option to include additional fields in structure VBAKKOM (communiction fields for maintaining the sales document header)
    USEREXIT_MOVE_FIELD_TO_VBAPKOM
    Option to include additional fields in structure VBAPKOM (communication fields for maintaining a sales item)
    USEREXIT_MOVE_FIELD_TO_VBEPKOM
    Option to include additional fields in structure VBEPKOM (communication fields for maintaining a sales document schedule line)
    USEREXIT_MOVE_FIELD_TO_VBSN
    You can use this user exit to include fields in structure VBSN (scheduling agreement-related change status).
    USEREXIT_MOVE_FIELD_TO_KOMKH
    You can use this user exit to include new fields for batch determination (document header).
    USEREXIT_MOVE_FIELD_TO_KOMPH
    You can use this user exit to include new fields for batch determination (document item).
    USEREXIT_CUST_MATERIAL_READ
    You can use this user exit to set another customer number in the customer material info record (e.g. with a customer hierarchy)
    USEREXIT_NEW_PRICING_VBAP
    Option for entry of preconditions for carrying out pricing again (e.g. changes made to a certain item field could be used as the precondition for pricing to be carried out again). Further information in MV45AFZB.
    USEREXIT_NEW_PRICING_VBKD
    Option for entry of preconditions for carrying out pricing again (e.g. changes to the customer group or price group could be set as the preconditions for the system to carry out pricing again). Further information in MV45AFZB.
    User-Exits in Program MV45AFZD
    USEREXIT_CONFIG_DATE_EXPLOSION
    The BOM is exploded in the order with the entry date. You can use this user exit to determine which data should be used to explode the BOM (explosion with required delivery date, for example).
    User exits in the program FV45EFZ1
    USEREXIT_CHANGE_SALES_ORDER
    In the standard SAP R/3 System, the quantity and confirmed date of the sales document schedule line is changed automatically if a purchase requisition is allocated, and it or the sales document is changed (for example, quantity, date).
    If you want to change this configuration in the standard system, you can define certain requirements in order to protect your sales orders from being changed automatically. Use this user exit for this purpose. Decide at this point whether the schedule lines are to be changed.
    User-Exits in Program RV45PFZA
    USEREXIT_SET_STATUS_VBUK
    In this user exit you can you can store a specification for the reserve fields in VBUK (header status). Reserve field UVK01 could, for example, be used for an additional order status (as for rejections status, etc.).
    The following workareas are available for this user exit:
    VBUK (header status)
    FXVBUP (item status)
    FXVBUV (Incompletion)
    USEREXIT_SET_STATUS_VBUP
    In this user exit you can you can store a specification for the reserve fields for VBUP (item status).
    The following workareas are available for this user exit:
    FXVBAP (Item data)
    FXVBAPF (Dynamic part of order item flow)
    FXVBUV (Incompletion)
    USEREXIT_STATUS_VBUK_INVOICE
    You can use this user exit to influence billing status at header level.
    User exits in the screens
    Additional header data is on screen SAPMV45A 0309, additional item data on screen SAPMV45A 0459. These screens contain the Include screens SAPMV45A 8309 or SAPMV45A 8459 as user exits.
    Fields which are also to be included in the sales document for a specific installation should be included on the Include screens for maintaining. If an application-specific check module is needed for the fields, this can be included in the Include MV45AIZZ. The module is called up in the processing logic of the Include screens.
    For field transports, you do not have to make changes or adjustments.
    Example
    A new field, VBAK-ZZKUN, should be included in table VBAK.
    If the check is defined via the Dictionary (fixed values or check table) the field must be included with the fullscreen editor in the Include screen SAPMV45A 8309. In this case, no change has to be made to the processing logic.
    User Exits in Program MV45AFZ4
    USEREXIT_MOVE_FIELD_TO_KOMK
    You can use this user exit to add or edit additional header fields in the communication structure - KOMK- for free goods determination. For more information, see the New Fields for Free Goods Determination IMG activity.
    USEREXIT_MOVE_FIELD_TO_KOMP
    You can use this user exit to add or edit additional item fields in the communication structure KOMP for free goods determination. For more information see the New Fields for Free Goods Determination IMG activity.
    User Exits in the SAPFV45PF0E and SAPFV45PF0C Programs
    EXIT_SAPFV45P_001
    You can use this user exit to decide whether intercompany billing data is used in the profitability segment for cross-company code sales, or whether the data comes from external billing (external customer, sales data from the selling company code.
    regards
    P.

  • How to Validate the user entred value

    Hi All
    I am new to APEX... :)
    Can any one send me the URL or material where i can go through and create sample applicaiton having the following functionalities
    1) Create a form for the user to enter the data
    2) Create users and give access
    3) Validate the user entered values (Validation of a e-mail filed or Phone no)
    Thanks & Regards
    Hari

    Hari,
    You should start on our Getting Started page (http://www.oracle.com/technology/products/database/application_express/html/getting_started.html). I would suggest you do the OBE. It will show you how to create an application, add validations (that is what will make a user enter data in your email and phone fields) and create users. It uses APEX Authentication which means that any developer within the workspace can access and run the application and that you can also create end-users from within your workspace that will only be able to run your applications (not access the development environment).
    It will definitely answer your questions -
    -- Sharon

  • How to make the line items of sales order cannot be deleted.

    Hi All,
    Is there any Enhancement spots or user-exits which make the line items of sales order cannot be deleted if item category is 'TAN'.
    Thanks in Advance,
    Sudhakar Reddy .A

    Hi All,
    If you doesn't want to delete sales order line items then we have write in the Include Program which has mentioned below and in the form .....endform.
    Program Name :  Include MV45AFZB
    _Example:_
    form userexit_check_xvbap_for_delet using us_error
                                              us_exit.
    IF .......
      US_EXIT = CHARX.
    ENDIF.
    endform.

  • How to retrieve the Line item Text

    Hello,
    I need to retrieve the Line item Text in the PO (Material PO text). Can anyone provide me a sample code? i need to display this in a smartform.
    I could not retrive it from the Function Module READ_TEXT.
    Can any one help me regarding this?
    Regards,
    kvsskirankumar

    HI,
    Use function module READ_TEXT to fetch PO line item text by passing id, language, name and object.
    For Ex:-
    CALL FUNCTION 'READ_TEXT'
      EXPORTING
        CLIENT             = SY-MANDT
        id                      = 'F01'
        language          = 'E'
        name                 = << concatenate PO number & line item>>
        object                = EKKO
      tables
        lines                   = g_t_ltext.
    Thanks & Regards
    Sudheer Madisetty

  • How to avoid XVBPA line item values while creating sales order

    Hi Friends
    I am creating Sales order using function module IDOC_INPUT_ORDERS, for that I am passing partner details through segment E1EDKA1.If I pass the same partner details(Partner number, name1,name4,city,postel code) which is same like customer master,
    I can able to book the order and entries are coming only one time in VBPA table(Header Item level).But if I change any value for the particular partner in the Input(For example Name4, there is no value in customer master but I added through program).Now its creating an order but its showing the entered partner informations in header level.When I checked the same in line item level, its not picking the values from header, its picking the values from customer master for that particular partner.
    So this line item also coming in VBPA table, because its different from header data.
    Anyone guide me, how to avoid this problem while booking order through program.
    Thanks
    Gowrishankar

    I am updating Ship-To-Party value in segment E1EDKA1 and calling IDOC_INPUT_ORDERS function module to create the sales order.
    In this case for the particular partner there is no NAME4 value in KNA1, I am passing some value through this segment E1EDKA1.
    So its creating an order with this new addresses , so its generating new ADRNR in VBPA header level.Thats fine.But the same time
    its not copying the same value from header to line item.
    In Line item level again its picking the address details from KNA1 for the particular partner number.So its showing Blank value in NAME4 field of line items.Its creating and spllitting issue, while creating delivery.
    Thanks
    Gowrishankar

  • How to clear the line items...

    hello friends,
    I am not able to clear line items with F.13 transaction for special G/L Account..i am inputing the values with the Transactions F-48 and F-43(In each transaction v have assigned the same assignment (BSIK-ZUONR)) line items has to be cleared based on Assignment....we can view the details in Tr.code-FBL1N.
    Can any one help me...plzzz
    vamshi

    Hi PK,
    1. Should we maintain OIM for all Excise G/Ls (BED, ECess, SHECess)?
    - Please DO NOT maintain OIM on BED, ECESS and HECESS, only to be maintained for Cenvat Clearing Account. Also note that clearing of Cenvat Clearing is not easy, as in standard SAP, the assignment field is not updated with the same information for the Dr. and cr. line items of Cenvat Clearing Account. You need to use an exit in Substitution for it to populate the P.O. no. and line item at the time of MIRO.
    2. How to clear the BED Excise GLs which is with OIM in our system, it is thru F.13 only?
    You can use F.13 only if the entries are matching not otherwise, else clear all of them manually if you have good control of your account balances.
    3. Can we activate or deactivate OIM any point of time, I mean can it be activated in case the G/L balance amount is not ZERO?
    OIM activation for a GL - Refer Note No.1356457.
    OIM Deactivation :  You can deactivate OIM after making the balance Zero on that Account and by changing the Message No. FH 190 to warning in OBA5.
    4. What is the use of T Code J2IUN, I have gone thru the SDN links, but I am not able to execute the screen. What parameter should we select while executing J2IUN, when we use Pay cenvat from ser tax cr and Pay ser tax from cenvat cr.
    J2IUN is to utllize Excise Duty. The liability of Excise duty is utilized from Excise balances of BED, PLA , Service tax etc.. as per business requirements.
    Hope this helps you.
    Regards,
    SAPFICO

  • How to validate the incoming field value and raise an alert message

    Dear all,
    I have the following structure
    If incoming value for the field externalid is empty then i have to raise a alert message to end user "externalid field is empty for the id : id number" and for all incoming values it should work. I used the following udf on field externalid with two arguments
    if(externalid.equals(""))
    throw new RuntimeException("externalid field empty for the following id : " +id);
    else
    return externalid;
    This is working fine for single record. But for many records(multiple occurences), this logic is not working as if records 2 and 3 fails it is showing exception externalid field is empty for the id : record 2.
    how to achieve the tranformation logic ?
    Regards
    Koti Reddy

    Hi Amit,
    I have tried the above udf, but still stuck-up.
    For the above structure shown in image, i have tested giving the following payload
    <?xml version="1.0" encoding="UTF-8"?>
    <ns0:upsertRequest xmlns:ns0="http://sap.com/xi/SFIHCM01">
       <sessionId/>
       <upsert>
          <type/>
          <sfobject>
             <id>1</id>
             <businessKeys>1</businessKeys>
             <type>1</type>
             <status>1</status>
             <externalId>1</externalId>
             <username>1</username>
             <firstName>1</firstName>
             <lastName>1</lastName>
             <mi>1</mi>
             <gender>1</gender>
             <email>1</email>
             <managerExternalId>1</managerExternalId>
             <hrExternalId>1</hrExternalId>
             <department/>
             <jobCode/>
             <division/>
             <location/>
             <timeZone>1</timeZone>
             <hireDate/>
             <empId/>
             <title/>
             <businessPhone/>
             <fax/>
             <addressLine1/>
             <addressLine2/>
             <city/>
             <state/>
             <country/>
             <zipCode/>
             <reviewFreq/>
             <lastReviewDate/>
             <matrixManagerExternalIds/>
             <defaultLocale/>
             <customManagerExternalIds/>
             <secondManagerExternalId/>
             <loginMethod/>
             <proxy/>
          </sfobject>
          <sfobject>
             <id>2</id>
             <businessKeys>2</businessKeys>
             <type>2</type>
             <status>2</status>
             <externalId>2</externalId>
             <username>2</username>
             <firstName>2</firstName>
             <lastName>2</lastName>
             <mi>2</mi>
             <gender>2</gender>
             <email>2</email>
             <managerExternalId>2</managerExternalId>
             <hrExternalId/>
             <department/>
             <jobCode/>
             <division/>
             <location/>
             <timeZone/>
             <hireDate/>
             <empId/>
             <title/>
             <businessPhone/>
             <fax/>
             <addressLine1/>
             <addressLine2/>
             <city/>
             <state/>
             <country/>
             <zipCode/>
             <reviewFreq/>
             <lastReviewDate/>
             <matrixManagerExternalIds/>
             <defaultLocale/>
             <customManagerExternalIds/>
             <secondManagerExternalId/>
             <loginMethod/>
             <proxy/>
          </sfobject>
          <processingParam>
             <name/>
             <value/>
          </processingParam>
       </upsert>
    </ns0:upsertRequest>
    No node is creating for success records, instead it throws exception that "externalid field is missing for the id": id     for empty externalid field value in second record.
    But my requirement is..... when i process 50 records, records with missing value for field externalid should raise an alert message to end user intimating him to check the externalid field for particular id. If the value for externalid field is present in incoming record/payload, then it should be passed to target system.
    How can i implement this logic ?
    Regards
    Koti Reddy

  • How to upload the line item data for the T-CODE CO12 by using LSMW

    Hi ALL
    i have to upload some data using the t-code CO12 by LSMW. can anybody help me where and what code i have to write to upload the multiple line-items in that.
    Thanks in advance.

    i think this follows the rule for BDC with table control, can you please give me some example code and also the step number where i have to write the code for uploading the multiple line items.
    thanks in advance !

Maybe you are looking for