Double Invoice check across company code

Hi All,
I have been trying to use the double invoice check functionality across company codes. i.e. when an invoice is posted in Company code A with ref no: xxx, and when I try to post a new inovice with the same reference ie. xxx in company code B, system does not give error message.
Please note: I have maintained message in application F5, no: 117 and 312.
Also in customization for double invoice check, I have unchecked "Check Company code" and checked "check reference" and "check invoice date"
I have also maintained the double invoice check flag in the vendor master.
Please help at the earliest.
Regards,
Ankush

Hi Ankush,
Good Day,
Duplicate invoice check across company code will not check for FI related invoice ( Like FB60)
But you can able to achive this with BTE ( SAMPLE_PROCESS_00001110 for FI Duplicate invoice check)
Steps for Implementing a BTE
(1)Goto transction FIBF menu Environment->Info System (P/S )
(2)Select the BTE you want to implement.
(3)Press button Sample function module
(4)This brings you to SE37 - Copy the sample function module to a Z-function module (First create a new function group for the function module) . Note: The name of the Z-functionmodule is not important
(5)Edit the code in the new function module
(6)Go back to transaction FIBF - Menu Settings->Products -> Of a customer and create a new product whicj identifies the new product . Remember to mark the Active field.
(7)Go back to FIBF menu Settings->P/S function modules->of a customer - Create an entry that links the BTE and Product with the new function module
Best Regards,
KSK

Similar Messages

  • Configuring double invoice check for vendor invoices posted through FB60

    Dear all
    Can anyone tell me how to configure double invoice check for vendor invoices posted through FB60.
    for miro documents..we can use Tcode OMRDC
    Is there any such tcode which can be used for configuring fi invoices for double checking..
    regards
    Expertia

    Dear Expertia,
    In FI,when checking for duplicated invoices, the system compares the
    following :Vendor, currency, company code, gross amount of the invoice,
    reference document number and Invoice document date.
    SAP Note 305201 clarifies this in a more details; please read it.
    The following fields must be identical for Duplicate invoice check
         Company code                              (BUKRS)
         Vendor number                             (LIFNR)
         Currency                                  (WAERS)
         Reference number                          (XBLNR)
         Amount in document currency               (WRBTR)
         Document date                             (BLDAT)
    If the document is having any one of the above filed different then the
    system does not consider it as a duplicate invoice.
    Also It will check duplicate invoice check in vendor master data and
    in posting key is there check box selected for sales related
    The setting you making in OMRDC i.e Materials management->Logistics
    Invoice Verification->Incoming Invoice ->Set Check for Duplicate
    Invoices is only valid for MM and not  FI invoices posted via FB60/FB65
    You should check the F1 help on field "Chk double inv." (LFB1-REPRF)
    in the relevant vendor master record (transaction FK03).
    Please also check, that message F5 117 has been set correctly in the
    IMG using this path:
    Financial Accounting -> Financial Accounting Global Settings ->
    Document -> Default Values for Document Processing -> Change Message
    Control for Document Control For Document Processing
    Finally & mainly, go to the relevant posting key is defined as sales
    related in transaction OB41. You have to flag this field if the
    duplicate invoice check should work.
    I hope this helps You.
    mauri

  • Double Invoice Check

    Hi
    How do we set the double invoice check in SPRO for Invoice Number and Reference field for Vendor Incoming Invoices
    Regards
    Sanil Bhandari

    Hi,
    Please go to vendor master > Payment Transaction Tab
    Check the Double Invoice option...
    System will carry out checking as mentioned below:
    Checking Logistics documents
    Firstly, the system checks whether the invoice documents have already been entered in the Logistics invoice verification; the system checks invoices that are incorrect, or invoices that were entered for invoice verification in the background.
    Checking FI documents
    The system then checks whether there are FI or Accounting documents that were created with the original invoice verification or the Logistics verification, and where the relevant criteria are the same.
    Checking Logistics documents
    In checking for duplicate invoices, the system compares the following characteristics by default:
    Vendor
    Currency
    Company code
    Gross amount of the invoice
    Reference document number
    Invoice document date
    If all of these characteristics are the same, the system issues a message that you can customize.
    When you enter credit memos or subsequent adjustments, the system does not check for duplicate invoices.
    Exception: Country-specific solution for Argentina, where invoices and credit memos are checked for duplicate documents.
    No message is issued if you enter a document that has previously been reversed.
    Dependencies
    The system only checks for duplicate invoices in Materials Management if you enter the reference document number upon entering the invoice.
    In Customizing for the Logistics invoice verification, you can specify that the following characteristics should not be checked:
    Reference document number
    Invoice document date
    Company code
    This means that you can increase the likelihood that the system will find a duplicate invoice, because you can reduce the number of characteristics checked.
    I Hope u found useful
    Please Reward Points if Found Useful
    Regards,
    Jigar

  • Double Invoice Check for Vendors

    Hi
    How can we create a check for Double Invoices for Vendors?
    regards
    Rupal

    HI
    Pls follow the path to set the status for Double Invoice Check
    IMG>Materials Management>Logistics Invoice Verification>Incoming Invoice>Set Check for Duplicate Invoices
    Moreever, in vendor master, you need to maintain the double invoice check tick in the company code data. I suggest you make this as a compulsory field in Field Status group for all your vendor account groups.
    Thanks & Regards
    Sanil K Bhandari

  • Vendor payment and customer recipts across company codes

    Hi all,
    We are having 4 company codes in US.The vendors and customers are spread across company codes.
    1st scenario:
    Vendor "abc" has a debit balance os 5000 in company code A. In company code B, the same vendor has credit balance of 10000.
    How can we net the balances in both compnay codes and pay the difference to the vendor. The client has separate house banks for each company code.
    2 nd scenario:
    A customer sends a check for 2500. which needs to be applied against company code A (500) and Company code B (2000)
    How does the payment and receipts needs to be applied across company codes. Kindly suggest.
    Regards,
    Amulya.
    Edited by: amulya chowdary on May 21, 2010 4:31 PM

    Hi,
    You need to configure cross company clearing thru OBYA.
    Your queries can be addressed either treating other company code as the vendor/customer or clearing to a inter company GL.
    Best Regards,
    Madhu

  • Control message "Purchase across Company codes is not allowed"

    Hello Gurus
    We are running SRM5.0 ECS using EP. If we attempt to create a SC that falls foul of the above validation, we get a message but only as a warning. Naturally if a warning, users will ignore and continue the purchasing process up to the point that the PO is created. However, when the PO is transferred to the ECC, we get the "Error in Process" status for the same message, but ECC validation routines have this set to an error and not a warning.  Evidently there is a discrepancy with severity between SRM and ECC. We want to ensure that SRM matches up to ECC so it is an error in SRM and not a warning.
    Searching the web, I see that the message id is KI-113. Can't be sure this is correct as the portal we use does not display the msg id. I've checked the message control config in SRM, and see nothing for the message. Further investigation reveals that in order to control messages through the config, you can only maintain those that are listed in BBPV_PDMSG. After searching for id or text, I still cannot see how I can escalate ths message to an error.
    Any ideas?
    Thanks
    Ian

    Hi peggy
    This message comes from your r/3 backend system. go to se91 KI - message no. 113 in sap r/3.
    it is not srm message.
    Error : Purchasing across company codes is not allowed
    BR
    Muthu
    Edited by: Muthuraman Govindasamy on Oct 13, 2008 10:17 AM

  • DOUBLE INVOICE CHECK VALIDATION

    Hi All,
    We have one client in USA ,Their requireemnt is as follows for Double invice check for FB60 ,FV60 AND F-47
    Double Invoice check required ,if REFERENCE NUMBER AND VENDOR NUMBER same for all business transactions irrespective of dates. In SAP there is Double check procedure with respective of Invoice date also. Can anybody help out in this regard?
    is it possible to add validation for that ? or If any BTE ?
    Rgds
    Suma

    Hello Lisa,
    Your first question,
    Yes system does not check MIRO invoice while posting FB60 invoice. Because when you post invoice with using FB60 transaction, system check BSIP table for duplication. But when you post MIRO invoice system doesn't fill BSIP table.
    So that your question answer is YES, you can register an invoice in MIRO with same reference without a warning.
    Your second question,
    BTE means Business Transaction Event. Those events are known as FI user-exit.
    So that when you posting an invoice with using FB60, system triggered on BTE 00001110 as i said on my previous message.
    I try to explain step by step how can you activate this BTE. But you need to ABAPer for giving warning message on this exit.
    Call FIBF transaction -> Settings -> Products -> ...of a customer
    Create a new line,
    Product : ZXX
    Text : BTE Products for FI Exit
    Product active : tick checkbox.
    Call SE37 for exit function and copy from FM SAMPLE_PROCESS_00001110 to ZFI_PROCESS_00001110. Then active your FM and go to FIBF transaction again.
    FIBF -> Settings -> Process Modules -> ...of a customer
    Define a new line.
    Process : 00001120
    Function Module : ZFI_PROCESS_00001110
    Product : ZFI
    And then you can some write ABAP code for validation and give warning message.
    In this FM, If you don't want to check duplicate invoice for your cases you can set export parameter e_nostd = 'X'.
    I hope it helps to you,
    Regards,
    Burak

  • Blocking logistic invoice verification at company code level

    Dear all,
    May I know what is the system setup (SPRO) for this:
    Blocking logistic invoice verification at company code level ?
    Thanks
    tuffy

    Hi There
    I think it can be solved in 2 ways,,
    1. Number range, if you have not defined for the particular company code for this year,,
    2. Authorization for the Comp Code level (Check with your basis team ,, it will be the easieast way to block it for CC level and when ever you want they can just remove the block, (insterad of doing the changes in config, if basis can control the authorization it will be the best way)
    Hope it helps,,
    Thanks
    Senthil

  • Transporttaion Cross Docking between EWM and ECC across company codes

    Seceanrio is as follows:
    We have an EWM managed site in GB, and an IM managed site in IE.
    We would like to use the transportation cross docking solution from within Service Parts Management to transfer goods from GB to IE, (ECC > EWM > ECC) across company codes.
    Is this possible within the standard SAP solution?
    Thanks in advance,
    Craig Bramhald

    Hi Hari
    Inter Company Purchase scenario works when the same material exists in both the company codes... I dont know how SAP would manage this in the case of Assets, when the Same Asset No is not existent in the other Co Code...
    However, Refer 1523976  PurchaseOrderERPRequest_In_V1:Asset account assignment fails
    This applies to EhP4 / EhP5 - But I dont know if you are using the enterprise service PurchaseOrderERPRequest_In_V1 ....
    If not, better create an OSS message to SAP and check with them mentioning the notes that you have mentioned in your message
    BR,Ajay M

  • Purchasing across company codes

    __Current System__
    We have 4 company codes with 4 purchasing org's; each for respective company codes.
    New Scenario
    Due to IT reorg, now we want to be able to purchase across company codes. Basically, single PO with multiple line items, coded to different cost center's, internal orders belonging to different company codes.
    What would be the best way to go about this?
    Points will be awarded.
    Thanks
    Amrish.

    Hi,
      Check whether the account assignment object (cost centre, wbs, etc) used belongs to the same company code in the purchase document
    Regards

  • Help - Error in PR BAPI :  Purchasing across company codes is not allowed..

    I have written a program to create Purchase Requisition.I am using two BAPIs.In the file i specify the old PR No, New Plant,Purch Group and Purch Org.It is actually a program to create a new PR in a new plant which is a copy of an Old PR in older plant.
    Program is below:
    I am getting the error Purchasing across company codes is not allowed..
    Please Help
    *& Report  ZMMB_BDC_ME51N_WO
    REPORT  ZMMB_BDC_ME51N_WO.
    INITIALIZATION.
    D A T A   D E C L A R A T I O N                                     *
      TYPES: BEGIN OF TY_TABDATA,
              BANFN TYPE EBAN-BANFN, " Purchase Requistion No
              WERKS TYPE MEREQ3211GRID-WERKS, "Plant
              EKGRP TYPE MEREQ3211GRID-EKGRP, "Purchasing Group
              EKORG TYPE MEREQ3211GRID-EKORG, "Purchasing Organization
             END OF TY_TABDATA.
      TYPES: BEGIN OF TY_CHECK,
                BANFN TYPE EBAN-BANFN, " Purchase Requistion No
                BNFPO TYPE EBAN-BNFPO, " Purchase Requistion Item No
                EBAKZ TYPE EBAN-EBAKZ, " PR Closed
             END OF TY_CHECK.
    Declaration of the Internal Table & Work Area.
      DATA:
             IT_TABDATA         TYPE  STANDARD  TABLE  OF   TY_TABDATA, " Internal Table for file
             WA_TABDATA         TYPE                       TY_TABDATA.
      DATA: IT_ITEM TYPE STANDARD TABLE OF BAPIEBAN ,
            WA_ITEM LIKE LINE OF IT_ITEM,
            IT_ITEM1 TYPE STANDARD TABLE OF BAPIEBANC,
            WA_ITEM1 LIKE LINE OF IT_ITEM1,
            IT_ACCOUNT TYPE STANDARD TABLE OF BAPIEBKN,
            WA_ACCOUNT LIKE LINE OF IT_ACCOUNT,
            IT_PRITEMTEXT TYPE STANDARD TABLE OF BAPIEBANTX,
            WA_PRITEMTEXT LIKE LINE OF IT_PRITEMTEXT,
            IT_SERVICES TYPE STANDARD TABLE OF BAPIESLL ,
            WA_SERVICES LIKE LINE OF IT_SERVICES,
            IT_SERVICES1 TYPE STANDARD TABLE OF BAPIESLLC ,
            WA_SERVICES1 LIKE LINE OF IT_SERVICES1,
            IT_SERVICETEXT TYPE STANDARD TABLE OF BAPIESLLTX,
            WA_SERVICETEXT LIKE LINE OF IT_SERVICETEXT,
            IT_CHECK TYPE STANDARD TABLE OF TY_CHECK,
            WA_CHECK LIKE LINE OF IT_CHECK.
       Global data Declaration
      DATA:   GV_YEAR(4)         TYPE C,
              GV_MNTH(2)         TYPE C,
              GV_DATE(2)         TYPE C,
              GV_DATUM(8)       TYPE C,
              GV_ANS TYPE C,
              W_FILENAME      TYPE  STRING.
    Declaration of the Internal Table with Header Line comprising of the uploaded data.
      DATA:  BEGIN  OF  IT_FILE_UPLOAD  OCCURS  0.
      INCLUDE  STRUCTURE  ALSMEX_TABLINE.  "  Rows for Table with Excel Data
      DATA:  END  OF  IT_FILE_UPLOAD.
    Batch Input Data for a single Transaction.
    Message of Call Transaction.
      DATA:  BDCDATA  LIKE  BDCDATA     OCCURS  0  WITH  HEADER  LINE,
             MSGTAB   LIKE  BDCMSGCOLL  OCCURS  0  WITH  HEADER  LINE.
    S E L E C T I O N - S C R E E N                                     *
      SELECTION-SCREEN:  BEGIN  OF  BLOCK  B1  WITH  FRAME TITLE TEXT-001,
                             BEGIN  OF  BLOCK  B2  WITH  FRAME TITLE TEXT-004.
      PARAMETERS: P_FNAME  LIKE  RLGRAP-FILENAME  OBLIGATORY.
      SELECTION-SCREEN:      END  OF  BLOCK  B2,
                         END  OF  BLOCK  B1.
    E V E N T : AT    S E L E C T I O N - S C R E E N                   *
    AT  SELECTION-SCREEN  ON  VALUE-REQUEST  FOR  P_FNAME.
      CALL FUNCTION 'KD_GET_FILENAME_ON_F4'
        EXPORTING
          STATIC    = 'X'
        CHANGING
          FILE_NAME = P_FNAME.
    E V E N T : S T A R T - O F - S E L E C T I O N                     *
    START-OF-SELECTION.
    Upload Excel file into Internal Table.
      PERFORM  UPLOAD_EXCEL_FILE.
      IF  NOT  IT_FILE_UPLOAD  IS  INITIAL.
      Confirm whether you want to proceed with the Upload.
        PERFORM  CONFIRM_UPLOAD.
        IF  GV_ANS  EQ  '1'.
      Organize the uploaded data into another Internal Table.
          PERFORM  ORGANIZE_UPLOADED_DATA.
          PERFORM BAPI_CALL.
        ENDIF.
      ELSE.
        LEAVE PROGRAM.
      ENDIF.
    *&      Form  UPLOAD_EXCEL_FILE
          text
    -->  p1        text
    <--  p2        text
    FORM UPLOAD_EXCEL_FILE .
      CALL FUNCTION 'ALSM_EXCEL_TO_INTERNAL_TABLE'
        EXPORTING
          FILENAME                = P_FNAME
          I_BEGIN_COL             = 1
          I_BEGIN_ROW             = 4
          I_END_COL               = 4
          I_END_ROW               = 9999
        TABLES
          INTERN                  = IT_FILE_UPLOAD
        EXCEPTIONS
          INCONSISTENT_PARAMETERS = 1
          UPLOAD_OLE              = 2
          OTHERS                  = 3.
      IF SY-SUBRC <> 0.
        MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
                WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
      ENDIF.
    ENDFORM.                    " UPLOAD_EXCEL_FILE
    *&      Form  CONFIRM_UPLOAD
          text
    -->  p1        text
    <--  p2        text
    FORM CONFIRM_UPLOAD .
      CALL FUNCTION 'POPUP_TO_CONFIRM'
        EXPORTING
          TITLEBAR       = TEXT-002
          TEXT_QUESTION  = TEXT-003
        IMPORTING
          ANSWER         = GV_ANS
        EXCEPTIONS
          TEXT_NOT_FOUND = 1
          OTHERS         = 2.
    ENDFORM.                    " CONFIRM_UPLOAD
    *&      Form  ORGANIZE_UPLOADED_DATA
          text
    -->  p1        text
    <--  p2        text
    FORM ORGANIZE_UPLOADED_DATA .
      DATA : GV_TOTROW TYPE I, "No of records
              GV_ROW TYPE I,
              LC_CNT(3) TYPE N.
      GV_TOTROW = 1.
      SORT  IT_FILE_UPLOAD  BY  ROW
                              COL.
      LOOP AT IT_FILE_UPLOAD.
        GV_TOTROW = IT_FILE_UPLOAD-ROW.
      ENDLOOP.
      GV_ROW = 1.
      WHILE GV_ROW <= GV_TOTROW.
        LOOP  AT  IT_FILE_UPLOAD WHERE ROW = GV_ROW.
          CASE  IT_FILE_UPLOAD-COL.
            WHEN '0001'.
              WA_TABDATA-BANFN = IT_FILE_UPLOAD-VALUE.
            WHEN '0002'.
              WA_TABDATA-WERKS = IT_FILE_UPLOAD-VALUE.
            WHEN '0003'.
              WA_TABDATA-EKGRP = IT_FILE_UPLOAD-VALUE.
            WHEN '0004'.
              WA_TABDATA-EKORG = IT_FILE_UPLOAD-VALUE.
          ENDCASE.
        ENDLOOP.
        GV_ROW = GV_ROW + 1.
        APPEND WA_TABDATA TO   IT_TABDATA .
        CLEAR :WA_TABDATA.
      ENDWHILE.
    ENDFORM.                    " ORGANIZE_UPLOADED_DATA
    *&      Form  BAPI_CALL
          text
    -->  p1        text
    <--  p2        text
    FORM BAPI_CALL .
      DATA:ITM_NO(4) TYPE N,LV_PERCENTAGE(3) TYPE N,
           LV_MSG(60),
           IT_RETURN TYPE STANDARD TABLE OF BAPIRETURN,
           WA_RETURN LIKE LINE OF IT_RETURN.
      DATA: BEGIN OF WA_RETURN1,
            BANFN TYPE EBAN-BANFN.
      INCLUDE  TYPE BAPIRETURN.
      DATA END OF WA_RETURN1.
      DATA:IT_RETURN1 LIKE STANDARD TABLE OF WA_RETURN1.
      DESCRIBE TABLE IT_TABDATA LINES ITM_NO.
      LOOP AT IT_TABDATA INTO WA_TABDATA.
        CALL FUNCTION 'BAPI_REQUISITION_GETDETAIL'
          EXPORTING
            NUMBER                               = WA_TABDATA-BANFN
           ACCOUNT_ASSIGNMENT                   = 'X'
           ITEM_TEXTS                           = 'X'
           SERVICES                             = 'X'
           SERVICE_TEXTS                        = 'X'
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_TEXT                     = IT_PRITEMTEXT
      REQUISITION_LIMITS                   =
      REQUISITION_CONTRACT_LIMITS          =
       REQUISITION_SERVICES                 = IT_SERVICES
       REQUISITION_SERVICES_TEXTS           = IT_SERVICETEXT
      REQUISITION_SRV_ACCASS_VALUES        =
      RETURN                               =
        COMPUTE LV_PERCENTAGE = ( ITM_NO / SY-TABIX ) * 100.
        CONCATENATE 'PROCESSING PURCHASING REQUISITION FOR OLD PR NUMBER ' WA_TABDATA-BANFN INTO LV_MSG.
        CALL FUNCTION 'RM_SAPGUI_PROGRESS_INDICATOR'
          EXPORTING
            PERCENTAGE = LV_PERCENTAGE
            TEXT       = LV_MSG.
        CLEAR:LV_PERCENTAGE ,LV_MSG.
        IF IT_TABDATA[] IS NOT INITIAL.
          SELECT BANFN BNFPO EBAKZ FROM EBAN INTO TABLE IT_CHECK FOR ALL ENTRIES IN IT_TABDATA
              WHERE BANFN = IT_TABDATA-BANFN AND EBAKZ = 'X'.
        ENDIF.
        LOOP AT IT_CHECK INTO WA_CHECK.
          LOOP AT IT_ITEM INTO WA_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ITEM WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
          LOOP AT IT_ACCOUNT INTO WA_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
            DELETE IT_ACCOUNT WHERE PREQ_NO = WA_CHECK-BANFN AND PREQ_ITEM = WA_CHECK-BNFPO.
          ENDLOOP.
        ENDLOOP.
        LOOP AT IT_ITEM INTO WA_ITEM.
          WA_ITEM-PLANT = WA_TABDATA-WERKS.
          WA_ITEM-PUR_GROUP = WA_TABDATA-EKGRP.
          WA_ITEM-PURCH_ORG = WA_TABDATA-EKORG.
          MODIFY IT_ITEM FROM WA_ITEM TRANSPORTING PLANT PUR_GROUP PURCH_ORG.
          MOVE-CORRESPONDING WA_ITEM TO WA_ITEM1.
          WA_ITEM1-PREQ_NO = ''.
          WA_ITEM1-STORE_LOC = ''.
          APPEND WA_ITEM1 TO IT_ITEM1.
          CLEAR WA_ITEM1.
        ENDLOOP.
        LOOP AT IT_ACCOUNT INTO WA_ACCOUNT.
          WA_ACCOUNT-PREQ_NO = ''.
          MODIFY IT_ACCOUNT FROM WA_ACCOUNT TRANSPORTING PREQ_NO.
        ENDLOOP.
        LOOP AT IT_SERVICES INTO WA_SERVICES.
          MOVE-CORRESPONDING WA_SERVICES TO WA_SERVICES1.
          APPEND WA_SERVICES1 TO IT_SERVICES1.
          CLEAR WA_SERVICES1.
        ENDLOOP.
        CALL FUNCTION 'BAPI_REQUISITION_CREATE'
       EXPORTING
         SKIP_ITEMS_WITH_ERROR                =
         AUTOMATIC_SOURCE                     = 'X'
       IMPORTING
         NUMBER                               =
          TABLES
            REQUISITION_ITEMS                    = IT_ITEM1
           REQUISITION_ACCOUNT_ASSIGNMENT       = IT_ACCOUNT
           REQUISITION_ITEM_TEXT                = IT_PRITEMTEXT
         REQUISITION_LIMITS                   =
         REQUISITION_CONTRACT_LIMITS          =
          REQUISITION_SERVICES                 = IT_SERVICES1
         REQUISITION_SRV_ACCASS_VALUES        =
           RETURN                               = IT_RETURN
          REQUISITION_SERVICES_TEXT            = IT_SERVICETEXT
         REQUISITION_ADDRDELIVERY             =
         EXTENSIONIN                          =
        READ TABLE IT_RETURN INTO WA_RETURN INDEX 1.
        IF WA_RETURN-TYPE = 'E'.
          CLEAR WA_RETURN.
          LOOP AT IT_RETURN INTO WA_RETURN WHERE TYPE EQ 'E'.
            WA_RETURN1-BANFN = WA_TABDATA-BANFN.
            MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
            APPEND WA_RETURN1 TO IT_RETURN1.
            CLEAR WA_RETURN1.
          ENDLOOP.
        ELSE.
          WA_RETURN1-BANFN = WA_TABDATA-BANFN.
          MOVE-CORRESPONDING WA_RETURN TO  WA_RETURN1.
          APPEND WA_RETURN1 TO IT_RETURN1.
          CLEAR WA_RETURN1.
        ENDIF.
        IF SY-SUBRC <> 0.
        ENDIF.
        CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
           EXPORTING
             WAIT          =
           IMPORTING
             RETURN        =
        REFRESH: IT_RETURN[],IT_ITEM[],IT_ACCOUNT[],IT_PRITEMTEXT[],IT_ITEM1[],IT_SERVICES[],IT_SERVICES1[],
                 IT_SERVICETEXT[].
      ENDLOOP.
      WRITE :10 'OLD PR NUMBER' COLOR COL_KEY, 25 'MESSAGE' COLOR COL_KEY.
      LOOP AT IT_RETURN1 INTO WA_RETURN1.
        WRITE:/10 WA_RETURN1-BANFN,25 WA_RETURN1-MESSAGE.
      ENDLOOP.
      CLEAR:IT_TABDATA[],WA_TABDATA.
    ENDFORM   .                 "BAPI_CALL

    Solved on Own

  • RFIDYYWT across company codes produces 1099 with multiple records per TIN

    We have multiple company codes that post 1099-MISC relevant payments to a common set of vendors.  All payments are processed through our main (paying) company code.
    All our company codes are one taxable entity to the federal government, with one TIN.  We are required to submit one file to the IRS.
    Unfortunately, when we execute RFIDYYWT across company codes we get multiple records per vendor, one for each company code, despite that the vendor has only one TIN.
    How may we customize the system so that a single execution of RFIDYYWT provides an IRS compliant file that aggregates common vendor records?
    Thank you in advance for your assistance.
    Regards,
    Otto Baskin
    P.S. Iu2019m happy to award points.

    Hi
    We have similar issue.. It's been long time.. but I thought of asking you.. Did you find solution? If so, can you please share.
    Thanks
    Srini

  • Double invoice check for customers

    Hello,
    I was surprised that there was no double invoice check functionality in AR. What I have done is in transaction OBA5, maintained the following entries:
    Message type - 117
    Online - E
    Batchl - E
    However when I put an invoice with the same reference for customer, there is no error message displayed. When I do the same for vendor invoice, it works fine. I am surprised that the functionality is active for AP and not for AR.
    Is there something that I am missing? Please advise.
    Regards
    Keyur

    Hello,
    We normally use transaction VF01. However, sometime we also use transaction FB70 to post direct FI Invoices relating to rebates etc.
    This is where the functionality of double invoice check will be useful.
    Thanks
    Keyur

  • Transaction code KO88 need to be check at company code leval

    Dear Experts,
    I need maintain authorization check at company code level for the transaction code KO88
    Can you suggest what are the better approaches/solutions to meet this requirement
    Thanks in Advance
    Guru Prasad

    Hi,
    it does not look like you can use standard authorization objects assigned to this transaction. This transaction is from CO module and this module does not use company codes directly. It uses controlling areas instead. You can see it in authorization object K_VRGNG which is checked in KO88.
    It does not look like there is a suitable BADI either. So if you are on Netweaver you can try to use enhancement framework. In program KO71 which corresponds to transaction KO88 is subroutine ACTIVITY_AUTHORITY_CHECK where FM K_VRGNG_AUTHORITY_CHECK is used to check authorization for object K_VRGNG. It looks to me that it's a good point to use implicit enhancement point of this subroutine to add additional authorization check. In your case check for company code attached to internal order. But you need to test it properly and it might work only for this transaction. So if user can start settlement from somewhere else that your additional check might not be performed.
    Cheers.

  • Double Invoice Check - Against the Delivery Note/ Bill #

    Dear All,
    I have a requirement here, Bit different from the Regular Double Invoice Check,
    I will receive the Material A, 10 different times, will do the GR 10 times & enter the Bill # & Challan # during GR. While posting the Invoice i want the system to check against which Bill # i am posting the invoice. Say during GR my Bill #s were 1 to 10. I receive the Invoice from my Vendor from 1 to 5 today, so i posted the invoice. After few days He will send a duplicate Invoice with Bill # as 5, & he will inform me that he lost original Invoice so he is sending the duplicate. As i have'nt posted Bill # 6 to 10, system will accept the Bill 5 also again. How can i avoid these things ?
    regds,
    CB

    Hi,
    Already I am maintaining these Bill # & Delivery Challan # during GR. My issue is during Invoice i want a check. In Invoice we have a reference field at header, If i am posting a single GR as a single invoice thats OK. But if I am posting more than 1 GR in single Invoice, where can i maintain the Bill # ? Any solutions pls ?
    regds,
    CB

Maybe you are looking for