Awkey for awtyp = 'BKPF' and awtyp = 'MKPF' in BKPF table
At my current client, there is the following situation in the BKPF table:
When the awtyp is 'BKPF' in the bkpf table, the awkey is number/company/year, as expected.
But when the awtyp is 'MKPF' in the bkpf table, the awkey is just number/year, with no intervening company code.
Is this standard practice for awkey in bkpf when awtyp = 'MKPF' ???
Or is this due to a configuration error that should be corrected ????
Hi,
Good morning and greetings,
That is standard SAP...If AWTYP is BKPF in the Object Key would be Document Number/Company Code/Year and in the case of MKPF it would be Document Number/Year as it pertains more to WA document type transaction which is from MM module and that is the reason the system will not be in a position to place the company code in the transaction.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan
Similar Messages
-
Very Urgent : Reterival of AWKEY field from BKPF table
Hi,
I am making a report in which i have to make relation of 2 fields BKPF-AWKEY and MKPF-MBLNR . but the problem is i am not to reterive data from it as i have to make inner join among these fields so data can be reterived fmo these tables.
plz provide me some guidelines as it is really urgent to me and help will be deinfately rewarded.First and foremost, i would advice you not to use words like VERY URGENT in your subject. You might want to go through the following link to understand the basic rules of the forum:
[Rules of Engagement|https://wiki.sdn.sap.com/wiki/display/HOME/RulesofEngagement]
For your requirement, below code might help you understand the logic in determining the link between BKPF and MKPF.
TYPES: BEGIN OF t_bkpf,
bukrs type bukrs,
belnr type belnr_d,
gjahr TYPE gjahr,
awtyp type awtyp,
awkey type awkey,
end of t_bkpf.
types: begin of t_mkpf,
mblnr type mblnr,
mjahr type mjahr,
end of t_mkpf.
data: i_bkpf type STANDARD TABLE OF t_bkpf,
i_mkpf type STANDARD TABLE OF t_mkpf.
data: wa_bkpf type t_bkpf,
wa_mkpf type t_mkpf.
PARAMETERS: p_bukrs type bukrs OBLIGATORY,
p_gjahr TYPE gjahr OBLIGATORY.
START-OF-SELECTION.
SELECT bukrs belnr gjahr awtyp awkey
into table i_bkpf
from bkpf
UP TO 20 ROWS
where bukrs = p_bukrs
and gjahr = p_gjahr
and awtyp = 'MKPF'.
IF NOT i_bkpf[] is INITIAL.
select mblnr mjahr from mkpf into table i_mkpf
for ALL ENTRIES IN i_bkpf
where mblnr = i_bkpf-awkey(10).
* and mjahr = i_bkpf-awkey+10(4).
ENDIF.
LOOP AT i_bkpf into wa_bkpf.
READ TABLE i_mkpf into wa_mkpf
with key mblnr = wa_bkpf-awkey(10)
mjahr = wa_bkpf-awkey+10(4).
IF sy-subrc eq 0.
write:/ 'Accounting Document:', 23 wa_bkpf-belnr,
35 'Material Document:', 55 wa_mkpf-mblnr.
ENDIF.
ENDLOOP. -
Regarding performance tuning for BSEG & BKPF table data fetch
Hi Friends:
Plz see the below select queries. This is really impacting the performance of my report. Plz suggest the steps to increase the performance of the report.Points will be rewarded.
Thanks:
FORM GET_DATA .
Selecting the Document number from BSEG table
SELECT BELNR BUKRS FROM BSEG INTO TABLE L_DOC_NO
WHERE BUKRS IN S_BUKRS
AND GJAHR = P_GJAHR
AND HKONT IN S_SAKNR.
IF SY-SUBRC <> 0.
MESSAGE ID 'ZTFI' TYPE 'E' NUMBER 006.
ENDIF.
CLEAR L_DOC_NO.
SORT L_DOC_NO BY BELNR.
Selecting the Document Number Based on the selection-screen.
SELECT BELNR BUKRS BUDAT CPUDT BLART MONAT FROM BKPF INTO TABLE
L_BKPF
FOR ALL ENTRIES IN L_DOC_NO
WHERE BUKRS = L_DOC_NO-BUKRS AND
BELNR = L_DOC_NO-BELNR AND
GJAHR = P_GJAHR AND
BUDAT IN S_BUDAT AND
MONAT IN S_MONAT.
IF SY-SUBRC <> 0.
MESSAGE ID 'ZTFI' TYPE 'E' NUMBER 006.
ENDIF.
*Fetch the Line Items
SORT L_BKPF BY BELNR.
SELECT BELNR BUKRS BUZEI HKONT SHKZG WRBTR FROM BSEG INTO TABLE
L_BSEG
FOR ALL ENTRIES IN L_BKPF
WHERE BUKRS = L_BKPF-BUKRS
AND BELNR = L_BKPF-BELNR
AND GJAHR = P_GJAHR
AND BUZEI BETWEEN '001' AND '999'.Hi,
Let me understand your code first.
The below code (the 2 selects) gets data from BSEG first and then gets data from BKPF table.
"*Selecting the Document number from BSEG table
SELECT BELNR BUKRS FROM BSEG INTO TABLE L_DOC_NO
WHERE BUKRS IN S_BUKRS
AND GJAHR = P_GJAHR
AND HKONT IN S_SAKNR.
IF SY-SUBRC 0.
MESSAGE ID 'ZTFI' TYPE 'E' NUMBER 006.
ENDIF.
CLEAR L_DOC_NO.
SORT L_DOC_NO BY BELNR.
"*Selecting the Document Number Based on the selection-screen.
SELECT BELNR BUKRS BUDAT CPUDT BLART MONAT FROM BKPF INTO TABLE L_BKPF
FOR ALL ENTRIES IN L_DOC_NO
WHERE BUKRS = L_DOC_NO-BUKRS AND
BELNR = L_DOC_NO-BELNR AND
GJAHR = P_GJAHR AND
BUDAT IN S_BUDAT AND
MONAT IN S_MONAT.
IF SY-SUBRC 0.
MESSAGE ID 'ZTFI' TYPE 'E' NUMBER 006.
ENDIF.
The below code, can't you avoid by taking all the fields required on your 1st select on BSEG table?
*Fetch the Line Items
SORT L_BKPF BY BELNR.
SELECT BELNR BUKRS BUZEI HKONT SHKZG WRBTR FROM BSEG INTO TABLE
L_BSEG
FOR ALL ENTRIES IN L_BKPF
WHERE BUKRS = L_BKPF-BUKRS
AND BELNR = L_BKPF-BELNR
AND GJAHR = P_GJAHR
AND BUZEI BETWEEN '001' AND '999'.
Please check the below blog on "Performance of Nested Loops" by Rob Burbank which would be really helpful.
/people/rob.burbank/blog/2006/02/07/performance-of-nested-loops
Hope this helps. Rwd points if helpful.
Thanks,
Balaji -
Equivalent tables for MARA, MAKT and MCH1 in the EWM system
Hi,
I would like to construct a report using the existing tables in EWM. But it turns out that it's somewhat different from the ECC system.
The material tables, MARA and MAKT and the batch table, MCH1 table are not there. I need the material number( like MARA-MATNR), material description/name(MAKT-MAKTX), the division ( MARA-SPART) and the batch number(MCH1-CHARG) and expiration date(MCH1-VFDAT).
Could someone provide the EWM equivalent for these tables and fields?
Thank you.
Best Regards,Table Name Short text
/SAPAPO/MAT_MTRX Matrices for Rules of Matrix Generation
/SAPAPO/MAT_RULE Rules for Setup Matrix Generation
/SAPAPO/MATAPN Alternative Product Number
/SAPAPO/MATBOD Product BOD Assignment
/SAPAPO/MATEXEC Product: Execution Data
/SAPAPO/MATGPVAL Product Group Values
/SAPAPO/MATGROUP Product Grouping
/SAPAPO/MATINFO Product Information
/SAPAPO/MATKEY Product
/SAPAPO/MATLANE TS: Master Data Table Product/Lane
/SAPAPO/MATLARES TS: Master Data Table Product/Lane/Resourc
/SAPAPO/MATLCP Materials Lifecycle Stages
/SAPAPO/MATLOC Location Product
/SAPAPO/MATLOCPR Partner-Dependent Location Product Attribu
/SAPAPO/MATLOCTD Time-Dependent Location Product Fields
/SAPAPO/MATLORES TS: Master Data Table Product/Location/Res
/SAPAPO/MATLOTSZ Lot Sizes & Days' Supplies for Material Ma
/SAPAPO/MATLPL Location Product Planner (with Planner Typ
/SAPAPO/MATLSIM Location Product with Planning Version
/SAPAPO/MATLSINH Location Product with Inheritance
/SAPAPO/MATLSPP SPP Relevant Location Product Attributes
/SAPAPO/MATLWH Location Product for Location Warehouse
/SAPAPO/MATLWHST Location Product for Location Whse and Sub
/SAPAPO/MATMAP Mapping Table for Products
/SAPAPO/MATMOD Model assignment of location product
/SAPAPO/MATNR_V MATNR for Foreign Key Checks
/SAPAPO/MATPACK Product: Packing/Packaging Data
/SAPAPO/MATPPM TS: Master Data Table Product/PPM
/SAPAPO/MATPRIO Product Priority Time & Version-Dependent
/SAPAPO/MATPRMRM Alternative units of measure for partner p
/SAPAPO/MATPRT Partner Product Master Data
/SAPAPO/MATPRTXT Partner product description
/SAPAPO/MATRELH Product-Relevant Hierarchies and Hierarchy
/SAPAPO/MATREPC Replenishment Control
/SAPAPO/MATREPCT Replenishment Control
/SAPAPO/MATRES TS: Master Data Table Location/Resource
/SAPAPO/MATRGPT Product Regional Pattern Assignment
/SAPAPO/MATRQ Requirement Profile in Material Master
/SAPAPO/MATRULET Text Table of Rules for Setup Matrix Gener
/SAPAPO/MATSBOD Product BOD Assignment with Planning Versi
/SAPAPO/MATSTOCK Stock Information
/SAPAPO/MATTXT Material Descriptions -
Find encumbrance for a PO and Invoice
All,
Can some one tell me how to find encumbrance for a PO and Invoice OR
the driving tables for joins?
Thanks.Hi,
Can some one tell me how to find encumbrance for a PO and Invoice OR
the driving tables for joins?
Please see:
How is the amount on active encumbrance field derived for a PO? (Doc ID 219903.1)
Where Are PO Encumbrance Type And Invoice Encumbrance Type Defined In R12? (Doc ID 781856.1)
R12: Validate and Funds Check Invoice Simultaneously Causes 'Encumbrance Acctg Fail' Hold (Doc ID 1269725.1)
R12: How to troubleshoot Funds Check Hold Issues on Payables Invoices (Doc ID 1055606.1)
R10.7/11/11i: PO: Purchasing Encumbrance Accounting Concepts and Process Model (Doc ID 1089107.1)
In addition running the below diagnostic script may help not only troubleshooting encumbrance related issue, but the script provided will give you the related tables for queries.
R12: Diagnostic Script to help troubleshoot Purchasing Accounting or Encumbrance Issues (Doc ID 1483743.1)
Thanks &
Best Regards, -
Batch nos for particular Delivery and line item no
Hi Gusy,
I am developing a report, which i need to display the Delivery and item no and batch detail for respective delivery and item. Is any table or function module, if I pass the Delivery and Item no to get the details
Ex: Delivery "80909080" and item "000010",
Thanks,
Gourisankar.Hi,
Check the table LIKP...You can pass the delivery number and item number to get the material and batch.
Once you get the batch number and material number , you can use BAPI_OBJCL_GETDETAIL , to get the batch characteristcis.
Regards,
Nagaraj -
Error when selecting bkpf table
select single belnr
into it_data-belnr
from bkpf
where awkey = it_vbrp1-vbeln and
blart = 'RV'.
above code i am using for selecting bkpf table , actually key field are not useful in this case & hws to use index.
plz reply.
Thanks,
JyotsnaHi,
select single belnr
into it_data-belnr
from bkpf
where awkey = it_vbrp1-vbeln and
blart = 'RV'.
In above query what is it_vbrp1-vbeln? if it is internal table you are missing some thing like For all entries in it_vbrp1.Check it once. -
BDC FOR FB02 to update XREF1_HD and XREF2_HD in BKPF table
Hi
I need to write BDC for FB02 To updated XREF1_HD and XREF2_HD in BKPF table
I need to put this code in Function module.
If i Call this function module is SE38 it shd add data of the above fiileds in BKPF tableHi,
In FBL3N you need to enter in Settings/Special Fields.( you need to create this fields previously in Customizing under following path>
FI/ Accounts receivable and Accounts payable/ Customer accounts/ Line Items/ Display line items/ Define additional fields for line item display.
Regards,
Miroslav -
Is there is any functional module avaibale to insert
bkpf and bseg table very urgent please
Thanks
RamkiFIUPDATE will not gnerate fi document after the updation.
I need Fi document after the it updated in the bseg and bkpf table
Thanks
regards
ramki -
Link between AUFK and BKPF table
Hi all,
Can anyone tell me the link between AUFK and BKPF table.
Thanks in advance
Regards
Neha Kapoorhi neha ,
1.first u have to get MBLNR from AUFM for that order
2.Next u have to call FM
<b>AC_DOCUMENT_RECORD</b>
I_AWTYP MKPF--->Constant
I_AWREF 4900003215--->MBLNR
I_AWORG 2004--->Year
I_AWSYS
I_AWTYP_INCL
I_AWTYP_EXCL
I_BUKRS
I_VALUTYP 0
X_DIALOG X
then u will get the Accounting Documents.
regards
prabhu -
Report for daily production and daily sales quantities
Can you Please any body let me know what fields and tables should I pick to generate a report for sales qty and production qty for a material on daily basis. we are using PP PI
Hi,
You can use table MSEG for that purpose. Try BUDAT-MKPF as one of the selection parameters and use
MBLNR-MKPF = MBLNR-MSEG
MJHAR-MKPF = MJHAR-MSEG
Sort the results in ERFMG-MSEG and ERFME-MSEG using
BWART-MSEG = 101 minus 102 (for production)
SOBKS-MSEG = E
BWART-MSEG = 601 minus 602 (for sales).
Above stuff might be useful to you for your development requirement provided you are having Sales Order specific production.
Thanks & Regards,
Abu Arbab A -
Tables for vendor invoice and payment
Hi Gurus.
I want to know from which tables i can get the information for folllowing points.
1. Vendor Invoices - Complete (Header and Item)
2. Vendor Payments Details Detail about payment method (check, wire, etc)
Please tell me tje table names.There is no specific table for header/item data for vendor invoice. Various information regarding vendor invoice (FB60) are stored in the following tables( note: Ignore the structures in the list ).
|Table Name |Table Description |
|/BEV3/CHKOMPAZVV |Append Structure CH -> CO PA |
|/CWM/ACCIT |Append Structure for Enhancement of Structure ACCIT in CWM |
|/CWM/KOMP |Catch Weight Management Enhancement |
|/DSD/TAXJURCD |Ship From Tax Jurisdiction Code: for Header Prc Comm Str |
|/SAPNEA/J_SC_LFA1 |Subcontractor Information |
|/SAPNEA/J_SC_LFB1 |Subcontracting Management |
|/SAPPSPRO/A_FI2_LONGNUM |IBU-PS: Append structure for structure NONBSEG |
|/SAPPSPRO/A_LONGNUMBER |additional fields for SPIIN number |
|/SAPPSPRO/EADD |Purchasing Document Header: Additional Data |
|/SAPPSPRO/EADD_DATA |Purchasing Document Header: Data Part Additional Information|
|/VSO/R_KNA1_A |Append to KNA1 for Vehicle Space Optimization |
|/VSO/R_KNA1_I |Additional Data for Vehicle Space Optimization for KNA1 |
|AACCHD_FMFG |US federal fields |
|AACCHD_PSO |IS-PS: ACCHD Append Structure for Payment Requests |
|AACCIT_GM |Append for Grants Management |
|AACCIT_PSO |IS-PS: ACCIT Append Structure for Payment Requests |
|AACCIT_SSP |Append for Payment Statistical Sampling Process |
|AACCIT_USFG |Append structure for US federal government |
|AAUSZ_CLR_USFG |Clearing information for US Fed (Tresury Confirmation) |
|ABKPF_PSO |IS-PS: BKPF Append Structure for Payment Requests |
|ABKPF_UMB |IS-PS: Append Structure for Transfer Transaction FMITPO |
|ABSID_PSO |IS-PS: Data appendix of open items customers |
|ABSIK_PSO |IS-PS: Data appendix of open items vendors |
|ABSIS_PSO |Local Authorities |
|ABUZ |Help Structure for Line Items to be Generated Automatically |
|ACCCR |Accounting Interface: Currency Information |
|ACCCR_FKEY |Key: Acctg Currency Data for Line Item Including Currency |
|ACCCR_KEY |Key: Accounting Currency Data for Line Item |
|ACCFI |Interface to Accounting: Financial Acctg One-Time Accts |
|ACCHD |Interface to Accounting: Header Information |
|ACCHD_KEY |Key: FI/CO Document Header |
|ACCIT |Accounting Interface: Item Information |
|ACCIT_EXTENSION |ACC Document: Additional Item Information |
|ACCIT_JV |Joint Venture Accounting |
|ACCIT_KEY |Key: FI/CO Line Item |
|ACCIT_WT |Withholding tax information for FI Interface |
|ACCRDF |Fields for Posting Small Differences: Preparation |
|ACC_DOCUMENT |Accounting document |
|ACC_KONTEXT |Context Info for FI Single Screen Transactions FB50 and FB60|
|ACERRLOG |Return Parameter |
|ACGL_HEAD |Fields for Document Header Entry Screen |
|ACGL_ITEM |Structure for Table Control: G/L Account Entry |
|ACSCR |Communication Structure for Field Modification SAPLFDCB |
|ACSPLT |Carrier for Split Information re: Current Account Line Items|
|ACSPLT_WTNEW |Proportion of New Withholding Tax |
|ACSPLT_WTOLD |Proportion of Old Withholding Tax |
|ADDR1_SEL |Address selection parameter |
|AEBPP_KNBK |Additional Fields Bank Data Biller Direct |
|AEBPP_LFBK |Additional Fields Bank Data Biller Direct |
|AFMIOI |Append for new fields ECC50/ERP |
|AFMIOI_USFG | SD order needs quantity |
|AFMISPS |Additional Fields for Table FMISPS |
|AFM_ACCIT_EXTENSION |Extension for FM Payment Update |
|AFM_FAGL_GLT0_ACCIT_EXT |Extension FM Account Assignments |
|AFM_FI_BKPF_SUBST |Append to Structure BKPF_SUBST |
|AFM_FMFCTF |Append for Fund Center substrings |
|AFM_FMFINCODE |Append for Fund substrings |
|AIFM01D |Append for IFM01D |
|AKNA1_FMFG |US Federal Government Customer Master Data Additional Fields|
|AKNA1_PSO |Local Authority Additional Fields |
|AKNB1_PSO |IS-PS: Customer Master Record, Additional Data (Co.Code) |
|AKNBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALFA1_FMFG |US Federal Government Vendor Master Data Additional Fields |
|ALFA1_PSO |Local Authority Additional Fields (Address) |
|ALFB1_FMFG |PS fields for company code-specific master data field |
|ALFB1_PSO |IS-PS: Data Appendix Vendor Master Record (Company Code) |
|ALFBK_PSO |Bank Details Dependent on Time and Account Holder |
|ALVDYNP |ALV dialog screen fields |
|ALV_S_FCAT |Field Catalog (for LVC and for KKBLO) |
|ALV_S_FILT |Filter Criteria (for LVC and for KKBLO) |
|ALV_S_GRPL |Group Levels (for LVC and for KKBLO) |
|ALV_S_LAYO |Layout (for LVC and for KKBLO) |
|ALV_S_PCTL |Structure for Checking Print in ALV |
|ALV_S_PRNT |Print settings (for LVC and KKBLO) |
|ALV_S_QINF |Structure for Quickinfos of Exceptions |
|ALV_S_SGRP |Field Groups (for LVC and for KKBLO) |
|ALV_S_SORT |Sort Criteria (for LVC and for KKBLO) |
|ANBZ |Help structure for asset line item |
|ANLZACCOUNT |Additional Account Assignment Objects in Asset Accounting |
|ANLZACCOUNT_FKBER |Account Assignment Objects: ANLZACCOUNT with Function Added |
|ARC_PARAMS |ImageLink structure |
|AT003_XBLNR2 |Append structure for US federal government |
|AUSZ1 |Clearing Table 1 |
|AUSZ2 |Clearing Table 2 |
|AUSZ_CLR |Assign Clearing Item to Cleared Items |
|AUSZ_CLR_ASGMT |Assgt of Clrg Items - Cleared Items with Acct Assignment |
|AUSZ_INFO |Open item data for clearing transactions |
|AVBKPF_FMFG |US federal |
|AVBKPF_PSO |IS-PS: Append Structure VBKPF for Payment Requests |
|AVBSEGDPSO |IS-PS: Append Structure VBSEGD for Payment Requests |
|AVBSEGKPSO |IS-PS: Append Structure VBSEGK for Payment Requests |
|AVIK |Payment Advice Header |
|AVIP |Payment Advice Line Item |
|BALHDR |Application log: log header |
|BALMT |Application Log: Structure for a formatted message |
|BAL_S_CLBK |Application Log: Return routine definition |
|BAL_S_CONT |Application Log: Context |
|BAL_S_MSG |Application Log: Message Data |
|BAL_S_PAR |Application Log: Parameter Name and Value |
|BAL_S_PARM |Application log: Parameters |
|BAPIASCONT |Business Document Service: File Content ASCII |
|BAPIBDS01 |Business Document Service: Reference Structure for BAPIs |
|BAPICOMFIL |BDS: Command File for Transport Entries |
|BAPICOMPO2 |SBDS: Enhanced Component Information |
|BAPICOMPO3 |SBDS: Enhanced Component Information |
|BAPICOMPON |Business Document Service: Component Table |
|BAPICONNEC |BDS: Structure for BDS Links |
|BAPICONTEN |Business Document Service: File Content |
|BAPIDPROPT |BDS: Structure for Properties |
|BAPIFILES |Business Document Services: Transfer Table for File Names |
|BAPIPROPER |BDS: Structure for Properties |
|BAPIPROPTL |BDS: Structure for KPRO Properties |
|BAPIQUERY |BDS Structure for Query Table |
|BAPIRELAT |Business Document Service: Relations |
|BAPIRET1 |Return Parameter |
|BAPIRETURN |Return Parameter |
|BAPISIGNAT |Business Document Service: Signature Table |
|BAPISRELAT |Business Document Service: Relationship Table with Signature|
|BAPIURI |Business Document Service: URI Table |
|BDCMSGCOLL |Collecting messages in the SAP System |
|BDCRUN |Batch input: Runtime analysis |
|BDIDOCSTAT |ALE IDoc status (subset of all IDoc status fields) |
|BDI_SER |Serialization objects for one/several IDocs |
|BDN_FKT |Business Document Navigator: Functions to be Excluded |
|BDWFAP_PAR |Parameters for application function module - IDoc inbound |
|BDWFRETVAR |Assignment of IDoc or document no. to method parameter |
|BDWF_PARAM |Parameters for workflow methods for IDoc inbound processing |
|BKDF |Document Header Supplement for Recurring Entry |
|BKDF_SUBST |Process Interfaces: Substitutable fields during posting |
|BKORM |Accounting Correspondence Requests |
|BKP1 |Document Header Supplement for Update |
|BKPF |Accounting Document Header |
|BKPFBU_ALV |Document Overview: Display Document Headers in ALV Grid Ctrl|
|BKPF_CARD |Credit Card: Append for BKPF |
|BKPF_LINE |Item Category for XBKPF_TAB |
|BKPF_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BKPF_USFED |Append structure for US federal government |
|BLNTAB |Document Number Table for Financial Accounting |
|BNKA |Bank master record |
|BNKAAPP |Appendix to Table BNKA |
|BNKT |Conversion of temporary to internal bank keys |
|BOOLE |Boolean variable |
|BSEC |One-Time Account Data Document Segment |
|BSEC_LINE |Item Category for XBSEC_TAB |
|BSED |Bill of Exchange Fields Document Segment |
|BSEE |Changeable Fields in the Line Item |
|BSEG |Accounting Document Segment |
|BSEGL |Document Segment: Fields Derived for Line Layout Variant |
|BSEGS |G/L Item Transfer Structure for Single Screen Transactions |
|BSEGT |Transfer Table for the Tax Postings to be Generated |
|BSEGZ |Financial Acctg Doc.Segment: Extras and Temp. Storage Fields|
|BSEG_ALV |Document Overview: Document Item Display in ALV Grid Control|
|BSEG_LINE |Item Category for XBSEG_TAB |
|BSEG_SUBST |Process Interfaces: Substitutable Fields During Posting |
|BSET |Tax Data Document Segment |
|BSEU |Line Item Additional Information (Update) |
|BSEZ |Line Item Additional Information (Online) |
|BSEZ_LINE |Line Item Category for XBSEZ_TAB |
|BSID |Accounting: Secondary Index for Customers |
|BSIK |Accounting: Secondary Index for Vendors |
|BSIP |Index for Vendor Validation of Double Documents |
|BSIS |Accounting: Secondary Index for G/L Accounts |
|BSIX |Index table for customer bills of exchange used |
|BTXKDF |Fields for Exch.Rate Difference Posting for Taxes |
|BVOR |Intercompany posting procedures |
|CACS_A_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_A_CUST_COND |Commissions: Customer Fields Condition Technique |
|CACS_A_FIELDSPRICING |Append for Condition Technique Fields from Commission System|
|CACS_S_CRM_SALES_COND |Additional CRM Fields (Construction) From Sales Order Area |
|CACS_S_CUST_COND |Condition Attributes |
|CACS_S_FIELDSPRICING |Comm.: All Condition Technique-Relevant Commission Fields |
|CACS_S_FSINS |Customer Fields for Condition Technique of Insurances |
|CCDATA |Payment cards: Database fields relevant to both SD and FI |
|CFW_LINK |CFW: Link Info of a Container |
|CI_COBL |Extension |
|CKI_ACCIT_ML |Transfer from MM to ML in accit-structure |
|CNTLSTRLIS |Control stream list |
|COBK |CO Object: Document Header |
|COBK_ONLY |Non-key fields only in COBK (INCLUDE structure) |
|COBL |Coding Block |
|COBLF |Coding block: Tax table structure |
|COBL_COKZ |Assignment types for CO account assignments |
|COBL_DB_INCLUDE |Include with Additional Account Assignments for DB Tables |
|COBL_EX |Coding Block for External Applications (Not CO/FI) |
|COBL_FI |Fields from COBL that Must not Be Overwritten in FI |
|COBL_FM |Additional Fields for FM |
|D010SINF |Generated Table for View D010SINF |
|D020S |System table D020S (screen sources) |
|D020T |Screen Short Description |
|DBSEG |Dialog Supplementation BSEG (Taxes) |
|DD02L |SAP Tables |
|DD03P |Structure |
|DD03V |Table fields view |
|DD07V |Generated Table for View DD07V |
|DD23L |Matchcode ID |
|DD32P |Interface structure for search help parameters |
|DDSHDEFLT |Description of a default value for search help fields |
|DDSHDESCR |Interface: elementary search helps of a search help |
|DDSHFPROP |Characteristics of search help parameters |
|DDSHIFACE |Interface description of a F4 help method |
|DDSHRETVAL |Interface Structure Search Help <-> Help System |
|DDSHSELOPT |Selection options for value selection with search help |
|DDSUX030L |Nametab Header, Database Structure DDNTT |
|DDSUX031L |Nametab Structure, Database Structure DDNTF |
|DDTYPES |Table of all Dictionary types and classes |
|DFIES |DD Interface: Table Fields for DDIF_FIELDINFO_GET |
|DISVARIANT |Layout (External Use) |
|DOKHL |Documentation: Headers |
|DPPROPS |General property structure for data provider |
|DTC_S_LAYO |Structure for Design of Double Table Control |
|DTC_S_TC |Structure for table controls in the double table dialog box |
|DTC_S_TS |Tab Title Structure |
|DYNPREAD |Fields of the current screen (with values) |
|E071 |Change & Transport System: Object Entries of Requests/Tasks |
|E071K |Change & Transport System: Key Entries of Requests/Tasks |
|EAPS_20 |Field Enhancements for EA-PS 2.0 |
|EDIDC |Control record (IDoc) |
|EDIDS |Status Record (IDoc) |
|EDIFCT |IDoc: Assignment of FM to log. message and IDoc type |
|EDIMESSAGE |Transfer Structure with all Sy Fields for T100 |
|EDI_DS |Status record for interface to EDI subsystem |
|EDI_HELP |Help Structure for Reference Fields in EDI Function Groups |
|EK05A |Communication Area Purchasing - Financial Accounting |
|ESKN |Account Assignment in Service Package |
|EUDB |Development Environment Objects |
|EUOBJ |Workbench: Development Objects |
|EXCLTAB_LINE |Lines of EXCLTAB with OK Code to be Deactivated |
|EXISTING_DOC |Original Document |
|F05ACTRL |Control Fields for SAPMF05A and Subprograms |
|FAGLBSEGL_S |Additional Sender Flds from General Ledger for Doc. Overview|
|FAGL_GLT0_ACCIT_EXT |Line Information for Document Splitting |
|FAGL_MIG_S_BUKRS_LEDGER |Combination of Company Code and Assigned Ledgers |
|FAGL_SPLIT_FLD_S |Characteristics Permitted for Split |
|FAGL_S_APPLICATION |Application and Subapplication |
|FAGL_S_BALDIM |G/L Characteristics of Document Split in New General Ledger |
|FAGL_S_BUKRS |Structure with Company Code |
|FAGL_S_BUKRS_EXT |Structure: Company Codes --> Ledgers |
|FAGL_S_CURTYPES |Currency Types of a Ledger |
|FAGL_S_MIG_001 |Structure for Table FAGL_MIG_001 & FAGL_MIG_001_S |
|FAGL_S_MIG_MGPLN_EXT |Structure: Extended Migration Plan Information |
|FAGL_S_T8G40_BS |Split Fields with Characteristic "Balance Sheet" |
|FCRD_VBKPF |Credit Card: Include for Appends for BKPF, VBKPF |
|FCRD_VBSEG |Include for Appends for VBSE* |
|FDM_AR_CASE_ATTR_1 |FSCM DM: |
|FDM_AR_LINE_ITEM |FSCM: DM |
|FDM_AR_RFPOS |FSCM-DM: Enhancemt of Line Item Disp. with Dispute Case Flds|
|FELD |Screen Painter fields (internal) |
|FICCO |Adjustment Values for External Document Items |
|FICCT |Totals Information for Interclient Posting |
|FICTX |Tax Information for ICT |
|FIELDINFO |Field attributes for a specific field |
|FIN1_PARAM |OBNG: Trans. structure for official doc. numbering (global) |
|FIN1_PARAM_FI |OBNG: FI parameters |
|FIN1_PARAM_MM |OBNG: MM Parameters |
|FIPEX_STRUC |Subfields Commitment Item |
|FIPOEXT |Help structure for line items to be generated automatically |
|FIREVDOC |Transfer Structure for Dialog Module FI_DOCUMENT_REVERS |
|FISTL_STRUC |Substructure Fund Center |
|FM01 |Financial Management Areas |
|FMBLSTRING_COMPONENTS |Component of the BL String |
|FMCI |Commitment items master data |
|FMDY |FIFM: Screen Fields |
|FMFCTR |Funds Center Master Record |
|FMFG_ACCIT_EXTENSION |Extention for all fields that have to be transfered into BL |
|FMFINCODE |FIFM: Financing code |
|FMFPO |FIFM: Commitment Item |
|FMHRBA_NEG_DOC_TYPES |HR Integration: Doc. Types for Negative Funds Commitments |
|FMHRBA_SETTINGS |Integration with HR: Settings |
|FMHRBA_VAD_SETTINGS |HR Integration: Generate Value Adjustment Docs for Changes |
|FMICCN |FM: Append Structure for FMIOI (CCN Fields) |
|FMIDATA |Common Data for Funds Management Actual Data |
|FMIDATAFI |Clean FI Data for Funds Management Actual Data |
|FMIDATAOI |Clean Open Item Data for Funds Management Actual Data |
|FMIFIIT |FI Line Item Table in Funds Management |
|FMIKEY |Common Key for Funds Management Actual Data |
|FMIKEYFI |FI - Key for Funds Management Actual Data |
|FMIKEYOI |Common Key for Funds Management Actual Data |
|FMIOI |Commitment Documents Funds Management |
|FMIOIKEY |Key for Table FMIOI |
|FMIOI_USFG | SD order needs quantity |
|FMIREF |Ref. Funds Management Actual Data to Preceding Document |
|FMISPS |General Parameters for Funds Management |
|FMIT |Totals Table for Funds Management |
|FMMRESERV |Include for the Reduction of Funds Reservations (FM) |
|FMRFC |Function Modules and their RFC Destinations |
|FMSP_SPLIT_FIELDS |PSM Fields used in multiple account splitting |
|FMT001 |Additional Customizing for Funds Management |
|FMUP00T |Update Profiles |
|FMUP01 |Update Control with Value Type Dependency |
|FMUP_INV_KEY |Extension for FM Update: FI Key of Invoice |
|FMUP_PAY_KEY |Extension for FM Update: FI Key of Payment |
|FS006 |Fields for Optical Archiving |
|FTCHECK |Foreign Trade: Import Simulation - Ctrl Fields for Pricing |
|FTEXTS |Communication Structure for Additional Components |
|FTGENERAL |Foreign Trade: General Fields Item |
|FUND_STRUC |Substructure Fonds |
|FVD_TZB0A |Append to TZBOA: Loans Fields |
|GLACCOUNT_CCODE |G/L Account Master Record: Company Code |
|GLACCOUNT_CCODE_DATA |G/L Account Master Record: Company Code - Data |
|GLACCOUNT_CCODE_INFO |G/L Account Master Record: Company Code - Information |
|GLACCOUNT_CCODE_KEY |G/L Account Master Record: Company Code - Key |
|GLX_ORG_INFO |Organizational Assignment |
|GMBSEGZ |Grants Management Add-on |
|GXXLT_H |XXL interface: horizontal features |
|GXXLT_O |XXL_interface: texts for online display |
|GXXLT_S |XXL interface: structure of the semantics table |
|GXXLT_V |XXL interface: vertical features |
|HELPVAL |Restrict Value Range - Transfer Table |
|HELP_INFO |Transfer Values for the Help Processor |
|HELP_VALUE |Structure or Function Module HELP_VALUE_GET_FOR_TABLE |
|HHM_COBL |Include for COBL from FM |
|IADDR_PSO |Local Authority Additional Fields (Address) |
|IBKPF_PSO |IS-PS: Include Structure BKPF Payment Request Doc.Header |
|ICDIND |Structures for generating change document update programs |
|ICON |Icons table |
|ICONS |Icons |
|ICURR |Interface for Currency Translation -
Wht r the standard tables for vendor customer and sales order report/
Hi wht r the standard tables for vendor and customer reports and is how in normal we cannot use them for vendor reporting and etc ?
Hi
Customer is related to Sales Module
So for a customer we fetch the reports of Sales orders , Deliveries and Billing doc's
CUstomer and Vendor related tables with important fields:
KNA1: Customer Master-General(KUNNR,NAME1,LAND1)
KNB1: Customer Master(Company Code)(KUNNR,BUKRS,PERNR)
KNC1: Customer Master Data (Transaction Figures)(KUNNR,BUKRS,GJAHR)
KNVK: Customer Master Contact Partner(PARNR,KUNNR,NAME1)
KNVV: Customer Master sales data(KUNNR,VKORG,VTWEG,KDGRP)
KNBK: Customer Bank Details(KUNNR,BANKS,BANKL,BANKN)
KNVH: Customer Hierarchy (HITYP,KUNNR,VKORG,VTWEG,SPART)
KNVP: Customer Master Partner Functions(KUNNR,PARVW,KUNN2)
KNVS: Customer Shipment data(KUNNR,VSTEL,TRANS)
KNVI: Customer Tax data(KUNNR,ALAND,TATYP)
LFA1: Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1: Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1: Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
Sales related Tables for a customer
VBAK: Sales Document(Header Data) (VBELN, KUNNR)
VBAP: Sales Document(Item Data) (VBELN,POSNR,MATNR,ARKTX,CHARG)
Enquiry, Quotation, Sales Order are differentiated based on Doc.
Type(VBTYP field) in VBAK,VBAP Tables( for Enquiry VBTYP = A,
for Quotation 'B' & for Order it is 'C'.)
LIKP: Delivery Table (Header Data)(VBELN,LFART,KUNNR,WADAT,INCO1)
LIPS: Delivery Table (Item Data)(VBELN,POSNR,WERKS,LGORT,MATNR,VGBEL)
(LIPS-VGBEL = VBAK-VBELN, LIPS-VGPOS = VBAP-POSNR)
VTTK: Shipment Table (Header Data)(TKNUM)
VTTP: Shipment Table (Item Data)( TKNUM,TPNUM,VBELN)
(VTTP-VBELN = LIKP-VBELN)
VTFA: Shipping Document Flow(TKNUM,VBELV,VBELN)
VTPA: Shipping Partners data(VBELN,PARVW,KUNNR,PERNR)
VTTS: Stages in Shipment(TKNUM,TSNUM,TSTYP)
VTSP: Transport Stage/Shipment Item Allocation(TKNUM,TSNUM,TPNUM)
VEKP: Handling Unit: Header(Packing)(VENUM,VSTEL)
VEPO: Handling Unit: Item (Packing)(VENUM,VEPOS,VBELN)
VBRK: Billing Table(Header Data)(VBELN,FKART,BELNR)
VBRP: Billing Table(Item Data)(VBELN,POSNR,FKIMG,NETWR,VGBEL,VGPOS)
(VBRP-AUBEL = VBAK-VBELN, VBRP-VGBEL = LIKP-VBELN)
Apart from these tables there are lot of other tables which starts with
V, but we use the following tables frequently.
VBUK: All Sales Documents status & Admn. Data(Header)(VBELN,VBTYP)
VBTYP= C(Sales Order) VBTYP=J(Delivery) VBTYP=M(Invoice)
VBUP: Sales Documents status & Admn. Data(Item)(VBELN,POSNR)
VBEP: Sales Doc. Schedule Lines Data(VBELN,POSNR,EDATU,WMENG)
VBKD: To get sales related Business data like Payment terms etc.(VBELN,ZTERM)
VBFA: sales document flow data(VBELV,VBELN,POSNV,VBTYP)
VBPA: Partner functions Data(VBELN,PARVW,KUNNR,LIFNR)
VEDA: Contract Data(VBELN,VPOSN)
VEDAPO: Contract Data(VBELN,VPOSN)
Vendor related MM tables
EBAN-- Pur.Reqn. Data (BANFN,BNFPO,BADAT,MATNR)
EBKN-- Purchase Requisition Account Assignment(BANFN,BNFPO,VBELN)
EINA- Purchase Info.Record (General Data)(INFNR,MATNR,LIFNR)
EINE-- Purchase Info.Record (Pur.Orgn Data )(INFNR,EKORG)
ELBK-- Vendor Evaluation Header Data(LIFNR,EKORG,KLASS)
EKKO-- Purchase Order Data (Header)(EBELN,BSTYP,BSART)
EKPO-- Purchase Order Data (Item)(EBELN,EBELP,MATNR)
RFQ and PO are differentiated by Doc Type(BSTYP)in EKKO table.
For RFQ it is A and for PO it is F.
MKPF-- GRN Data (Header) (EBELN,BLDAT,BUDAT,XBLNR,BKTXT)
MSEG-- GRN Data (Item)(MBLNR,BWART,LIFNR,MATNR,EBELN)
Apart from this there are lot of tables which begin with 'M'& 'E', but we
use the following very often.
EKBE--PO History Data (EBELN,EBELP,BELNR,BLDAT,MATNR,VGABE)
EKBZ--PO History with delivery Costs(EBELN,BELNR,LIFNR,XBLNR)
EKET--Schedule lines data of a PO (EBELN,EINDT,SLFDT)
EKES--Vendor Confirmations Data(EBELN,EBTYP,EINDT,XBLNR)
Reward points if useful
Regards
Anji -
Table where I have entry for material document and Accounting doc.(GR/IR)
Hi all,
When GR/IR clearing is done manually using MR11 t.code,a material document gets posted.
Looking at the PO order history against the line item for which the GR/IR clearing is made,this material document appears. When clicked on material document and select the followon document, we get the accounting document.
My question is:
If we have to take a table entry download for all these together how do I do it.
Usually based on the material document number from table EKBE, we are giving the same number in object key in BKPF table and obtaining the same. This is a cumbersome process.
Do I have a table in SAP where if I enter the PO and the line item. I get the material document posted against it as well as the FI document(accounting document)
Your inputs are highly appreciated.
Regards
AravindHi,
I don't think there is a table which will have both MM and FI document numbers. The approach what you have adopted is right. If it is a regular requirement, you can develop an ABAP report for this.
Thanks
Murali. -
RBKP and BKPF table update from MIRO
Hi All,
I am using the BADI BADI_FDCB_SUBBAS01 to add a custom field in MIRO transaction. The added custom field is getting updated in RBKP transaction.
I also want to update the custom field data in BKPF table, but i dont know when the BKPF table gets updated in MIRO transaction.
Can you help me where the BKPF table will get updated. Is there any BADI for updating the custom fields in table BKPF via MIRO?
Thanks and Regards,
VijayHi Baskar,
I have done this thing from MIRO transaction to update BKPF table. Please check the below code.
METHOD if_ex_badi_fdcb_subbas01~put_data_to_screen_object.
CONSTANTS:
c_bkpf_xref1(25) TYPE c VALUE '(SAPLFDCB)BKPF-XREF1_HD'.
FIELD-SYMBOLS: <fs_bkpf_xref1> TYPE ANY.
fill interface attributes from importing paramters
me->if_ex_badi_fdcb_subbas01~invfo = im_invfo.
ASSIGN (c_bkpf_xref1) TO <fs_bkpf_xref1>.
IF sy-subrc = 0.
<fs_bkpf_xref1> = me->if_ex_badi_fdcb_subbas01~invfo-zlet_number.
ENDIF.
ENDMETHOD.
METHOD if_ex_badi_fdcb_subbas01~get_data_from_screen_object.
CONSTANTS:
c_bkpf_xref1(25) TYPE c VALUE '(SAPLFDCB)BKPF-XREF1_HD'.
FIELD-SYMBOLS: <fs_bkpf_xref1> TYPE ANY.
fill export parameters from interface attributes
ex_invfo = me->if_ex_badi_fdcb_subbas01~invfo.
ASSIGN (c_bkpf_xref1) TO <fs_bkpf_xref1>.
if sy-subrc = 0.
<fs_bkpf_xref1> = ex_invfo-zlet_number.
endif.
ENDMETHOD.
After passing the data through field symbols, then you need to update the BKPF table using the BADI AC_DOCUMENT. Refer the below code.
METHOD if_ex_ac_document~change_after_check.
variable declaration
DATA: lv_let_number TYPE zisr_let_number,
lv_field TYPE char18 VALUE '(SAPLMRMP)xaccit[]',
lv_let_field TYPE char27 VALUE '(SAPLMR1M)RBKPV-ZLET_NUMBER'.
Field symbol declaration
FIELD-SYMBOLS : <ft_accit> TYPE accit_t,
<fs_accit> TYPE accit,
<fv_let_number> TYPE ANY.
Constant declaration
CONSTANTS : lc_miro TYPE sytcode VALUE 'MIRO'.
Check for transaction code MIRO
IF sy-tcode EQ lc_miro.
ASSIGN (lv_field) TO <ft_accit>.
CHECK sy-subrc EQ 0.
ASSIGN (lv_let_field) TO <fv_let_number>.
CHECK sy-subrc EQ 0.
Assign the letter number to BKPF table field XREF1_HD
LOOP AT <ft_accit> ASSIGNING <fs_accit>.
lv_let_number = <fv_let_number>.
<fs_accit>-xref1_hd = lv_let_number.
ENDLOOP.
ENDIF.
ENDMETHOD.
Maybe you are looking for
-
What is the difference between Public and Protected Attributes
hi ppl, what is the difference if i declare attributes under public or protected to access the private method.for both (public or private) section iam getting the same result. CLASS CL DEFINITION. *protected section. public section. DATA:
-
Pages won't sync between iPad and Macbook
I cannot get my pages to sync between iPad and Macbook. I regularly go back and forth between the two because it's easier to read/edit on iPad and easier to type/copy-paste web info on Macbook. I'm finding right now that I have done a multitude of ed
-
I set up sync right before a new install of windows 7. I cannot get my sync to set up properly.
I had signed up and set up sync right before a new install of windows 7. I made sure Firefox stated the data was sent to the server before letting IT take over(company policy). I had made sure I used the sync code input on my PC from my Iphone before
-
I just downloaded JDeveloper 3.2 and was doing some playing around with the JSPs. One thing I was waiting for was being able to use custom tags. I ran into a bit of a problem - not sure if its a bug or an error on my part. The following JSP page caus
-
Many times when logging in (seems to be manly when I start by clicking 'my questions' - I also have this bookmarked because it's the most sensible place for me to start when visiting these discussion forums) I get an error saying "page not found". Th