0001025810

3
SAP Note Header Data Symptom When you make postings using the accounting interface, the document header text remains empty in the created FI document even though text was transferred in the interface parameter ACCHD-BKTXT. If the document header text is set as a required entry field in the used document type (transaction code OBA7), the posting is rejected with error message F5 480. Other Terms AC_DOCUMENT_CREATE, AC_DOCUMENT, F5 480, EXIT_SAPLV60B_001 Reason and Prerequisites You implemented the BAdI AC_DOCUMENT. The BAdI methods change_initial and change_after_check allow certain fields to be changed at line item level and document header level. At document header level, only the field BKTXT is released for change at the moment. As a result, the problem occurs only for the document header text. To determine whether you have a BAdI implementation active for AC_DOCUMENT, call transaction SE18, enter AC_DOCUMENT in the "definition name" field (before Release ECC 6.00) or in the "BAdI Name" field (since Release ECC 6.00), and choose "Implementation -> Overview" or "Enhancement Implementation -> Overview" in the menu. If your own implementations are displayed (Y*, Z*,...), correct this by proceeding as described in the Solution section. If the implementation is J_3RF_FBCJ_PROC, implement Note 938829. If other implementations delivered by SAP are displayed, proceed as described in the Solution section. If the BAdI delivered by SAP does not correspond to the recommendation under the Solution section, open a customer message with reference to this note using the components that belong to the BAdI implementations. If no implementations are displayed (or all implementations for other definitions are displayed), the problem has a different cause. Solution If there are no document headers changed in the BAdI implementation, the BAdI has to be implemented in such a way that in each case the statement MOVE-CORRESPONDING im_document-header to ex_document- header. or an equivalent sequence has to be processed in the BAdI in the relevant place. If the export parameter ex_document-header is not provided from the import parameter im_document- header, the fields contained here are deleted (at the moment, BKTXT only). If you only want to implement one of the BAdI methods change_initial or change_after_check, this statement has to be in both methods because both methods are executed if the BAdI is active. Validity 1025810 - Field BKPF-BKTXT (doc header text) empty in the FI document Version 4 Validity:  03/08/2011 - active Language English Released On 03/08/2011 17:34:33 Release Status Released for Customer Component  AC-INT Accounting Interface FI-AP-AP-A Posting/Clearing/Special General Ledger  FI-AP-AP-J Integration/Accounting Interface  FI-AR-AR-A Posting/Clearing/Special General Ledger  FI-AR-AR-J Integration/Accounting Interface  FI-GL-GL-A Posting/Clearing  FI-GL-GL-J Integration/Accounting Interface Priority Recommendations / Additional Info Category Consulting Software Component From Rel. To Rel. And Subsequent SAP_APPL  500  500  600  600  Other Components

Upload: kelly-reed

Post on 15-Oct-2015

96 views

Category:

Documents


0 download

DESCRIPTION

sap note 1025810

TRANSCRIPT

  • 5/25/2018 0001025810

    1/3

    SAP Note

    Header Data

    Symptom

    When you make postings using the accounting interface, the document header text remains empty in thecreated FI document even though text was transferred in the interface parameter ACCHD-BKTXT.If the document header text is set as a required entry field in the used document type (transactioncode OBA7), the posting is rejected with error message F5 480.

    Other Terms

    AC_DOCUMENT_CREATE, AC_DOCUMENT, F5 480, EXIT_SAPLV60B_001

    Reason and Prerequisites

    You implemented the BAdI AC_DOCUMENT.The BAdI methods change_initial and change_after_check allow certain fields to be changed at line

    item level and document header level.At document header level, only the field BKTXT is released for change at the moment. As a result,the problem occurs only for the document header text.To determine whether you have a BAdI implementation active for AC_DOCUMENT, call transaction SE18,enter AC_DOCUMENT in the "definition name" field (before Release ECC 6.00) or in the "BAdI Name"field (since Release ECC 6.00), and choose "Implementation -> Overview" or "EnhancementImplementation -> Overview" in the menu.If your own implementations are displayed (Y*, Z*,...), correct this by proceeding as described inthe Solution section.If the implementation is J_3RF_FBCJ_PROC, implement Note 938829.If other implementations delivered by SAP are displayed, proceed as described in the Solutionsection. If the BAdI delivered by SAP does not correspond to the recommendation under the Solutionsection, open a customer message with reference to this note using the components that belong to theBAdI implementations.If no implementations are displayed (or all implementations for other definitions are displayed),the problem has a different cause.

    Solution

    If there are no document headers changed in the BAdI implementation, the BAdI has to be implementedin such a way that in each case the statement MOVE-CORRESPONDING im_document-header to ex_document-header. or an equivalent sequence has to be processed in the BAdI in the relevant place.

    If the export parameter ex_document-header is not provided from the import parameter im_document-header, the fields contained here are deleted (at the moment, BKTXT only). If you only want toimplement one of the BAdI methods change_initial or change_after_check, this statement has to be inboth methods because both methods are executed if the BAdI is active.

    Validity

    1025810 - Field BKPF-BKTXT (doc header text) empty in the FI document

    Version 4 Validity:03/08/2011 - active Language English

    Released On 03/08/2011 17:34:33

    Release Status Released for Customer

    Component AC-INT Accounting Interface

    FI-AP-AP-A Posting/Clearing/Special General LedgerFI-AP-AP-J Integration/Accounting Interface

    FI-AR-AR-A Posting/Clearing/Special General Ledger

    FI-AR-AR-J Integration/Accounting Interface

    FI-GL-GL-A Posting/Clearing

    FI-GL-GL-J Integration/Accounting Interface

    Priority Recommendations / Additional Info

    Category Consulting

    Software Component From Rel. To Rel. And Subsequent

    SAP_APPL 500 500 600 600

    Other Components

  • 5/25/2018 0001025810

    2/3

    References

    This document refers to:

    SAP Notes

    This document is referenced by:

    SAP Notes (4)

    602 602 603 603 604 604 605 605 606 606

    1685206 Document header text deleted in accounting interface

    1057713 Segment substitution when posting with the AC interface

    938829 Document header text cleared after implemet. of note 909825

    837859 MIRO: Text transfer to accounting document

    938829 Document header text cleared after implemet. of note 909825

    837859 MIRO: Text transfer to accounting document

    1685206 Document header text deleted in accounting interface

    1057713 Segment substitution when posting with the AC interface

  • 5/25/2018 0001025810

    3/3