This can be cleared itseld in MIRO or its can be done in F-44. In all case the link is document number. BKPF, BSEG- belnr. MKPF, MSEG- mblnr, here you can also find PO number easily (ebeln) BSAK, BSIK- reference doc number (no SAP access so could'nt find the field name) Regards. Vijai.
SE16_BSEG: Data Browser BSEG FI - Information System: 8 : RSSG_BROWSER: Simple Data Browser: Basis - BW Service API: 9 : SE80: Object Navigator Basis - Repository Browser: 10 : SU01: User Maintenance Basis - User and Authorization Management: 11 : SM30: Call View Maintenance Basis - Table Maintenance Tool: 12 : RSA3: Extractor Checker Basis
ACDOCA contains all fields (360+) Table ACDOCA contains all fields (360+) required for G/L, CO, FI-AA, ML, and CO-PA; Table ACDOCA has fields from CO, ML, and FI-AA that aren’t in table BSEG. Additional Features of ACDOCA. No Limitation of 999 Document Line Item: Due to the 999-document line item posting limitation, table BSEG is usually
(1) So, when the data gets archived from ACDOCA? As you may have noticed already, in the chain mentioned in (2) above, the data is still lying there in ACDOCA, but with status (field BSTAT) updated for archived documents. Even the records may increase with FI totals archiving, which creates a balancing line for comprehensive reporting.
SKAT is a standard Financial Accounting Transparent Table in SAP FI application, which stores G/L Account Master Record (Chart of Accounts: Description) data. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition. I have a requirement to change field value of Net Due Date (BSEG-NETDT) base on a custom logic. This custom logic is base on Business Partner master data and Sales Orders data also. Every time an Invoice documents created (using tcode VF01, FB60, FB70, MIRO), this enhance will be triggered. But I can not find any BTE events, Exit, Enhance, BAdI it is 1:1 and fields have exactly the same names ( (MANDT), BUKRS, BELNR, GJAHR, BUZEI), however BSET contains tax data, which means there won't be BSET entry for each BSEG entry. Line Item. Rajasekhar. I think line item in BSEG and BSET are different.
But this recommendation is flipped in S/4 HANA. There are two major shortcomings of Costing based COPA. First, it is difficult to reconcile with account books due to timing difference between
Billing. VBRP. VBRP is a standard Billing Transparent Table in SAP SD application, which stores Billing Document: Item Data data. You can use the transaction code SE16 to view the data in this table, and SE11 TCode for the table structure and definition.
2 Answers. S/4 HANA combines data structure of different components (F1,AA,CO-PA) into a single line item table called ACDOCA. Those "eliminated/replace Tables" (like MSEG) seem to still be there, but they are not, at least not on DB-Level. What we see and what looks like them, are just Proxy-Objects, CDS-Views to well "emulate" the removed
1. Get the main program of the Tcode (order), by system status menu facility. 2. Goto se38 and give the main program name and click the. Environmental Analysis button, the icon adjacent to where-used three pegged icon. this will list the tables . narrow down to FI segment and find out. Wishes, Rajagopalan.
\n difference between bseg and acdoca
If the currency type of the controlling area is defined as second or third local currency in FI, this currency type is filled not only in the general ledger view of the FI postings (table ACDOCA, field KSL) but also in the entry view (table BSEG, fields DMBE2 etc.). The controlling area currency is thus integrated with FI.
OSS 2856765 - telling that table BSEG is not filled anymore here - is also very interesting in this context. ACDOCA-BSTAT = 'U' is an interesting one (i.e. "not in BSEG anymore") mentioned in note OSS2297729 - and can be seen in "document status" in the depreciation postings inside this blog. Again, thanks a lot. Inspiring. Thomas The information from BSEG is available in Universal Journal table ACDOCA, but from a process standpoint, BSEG is still being used. Also note that the field names are not identical in these two tables, e.g. Trading Partner is having a field name of VBUND in table BSEG and RASSC in table ACDOCA; Cost Center is having a field name of KOSTL in hvYX.
  • w1b7nt0yph.pages.dev/384
  • w1b7nt0yph.pages.dev/380
  • w1b7nt0yph.pages.dev/127
  • w1b7nt0yph.pages.dev/41
  • w1b7nt0yph.pages.dev/145
  • w1b7nt0yph.pages.dev/441
  • w1b7nt0yph.pages.dev/342
  • w1b7nt0yph.pages.dev/106

    • difference between bseg and acdoca