In addition to Weibo, there is also WeChat
Please pay attention
WeChat public account
Shulou
2025-01-16 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Internet Technology >
Share
Shulou(Shulou.com)06/02 Report--
S4 HANA material Certificate form MATDOC
In ECC, material vouchers are mainly divided into title table MKPF and line item table MSEG to store. In addition, there is a set of current inventory tables (including MARD, MSLB, MCHB, etc.) and historical inventory tables (including MARDH, MSLBH, MCHBH, etc.).
In S/4HANA, all these material vouchers, inventory and historical inventory tables are replaced by a MATDOC table. The new MATDOC records all material voucher data and other attributes and is no longer recorded in the MKPF and MSEG tables. The actual inventory data is no longer recorded, but is calculated in real time against the MATDOC table. This solves the problem of fetching numbers from various inventory tables in the past, although SAP can still fetch numbers from old tables through CDS (CORE DATA Service, similar to database view).
But now that we have new watches, we can certainly get inventory data directly from MATDOC. Let's take a specific example of the link between the MSEG and MATDOC tables in the HANA database. For example, in the se16n query table MSEG, you see that there are 55 pieces of data
Similarly, we see 55 records in the se16n query table MATDOC.
Both tables can be queried, so let's try using transactional DBACOCKPIT to check the correct entries by directly querying the database query of the database. Check the MATDOC first as follows
When you run a direct select query from MATDOC at the database level, it displays 55 values. Now let's try running the same program for MSEG and see if we can query 55 records as well.
It is displayed as 0. So it is clear that there are no entries in the MSEG in the HANA database. When running SE16N, it only points internally to MATDOC. This is a screenshot of SE11. Go to the Extras menu of table MSEG and we will see these details. SAP introduces a concept called "replacement object", which mentions the name of the CDS view. It was called a Proxy object until version 1709, and SAP seems to have renamed it "Replacement Object" to avoid confusion caused by the word "Proxy".
Appears as a replacement for MSEG,NSDM_E_MSEG. Therefore, when we access MSEG in a SE16N or custom program, SAP uses this CDS view logic, which CDS view gets data from MATDOC. You can see the logic in the screenshot below. Provide the view name for the CDS view NSDM_E_MSEG in SE11. We will get the following details, which also provide the DDL definition name and DDL SQL view name (NSDM_V_MSEG).
The NSDM_V_MSEG view in SE11 clearly shows that it fetches data from MATDOC.
The final section of the DDL definition discusses any custom or additional fields and how to handle them in these replacement objects. You need to use the Extend view and attach custom fields to the Eclipse editor.
The above concept of replacement object / proxy object is mainly introduced to avoid confusion / change in custom programs dealing with MSEG. Therefore, if the custom program chooses from MSEG, it will still be similar to what we saw in the SE16N screenshot above.
At this point, the relationship between the new table MATDOC and the original material certificate form is almost clear, and you can leave a message for discussion if you have any other findings.
The affected tables are listedbelow:
Table
Table description
DDL Source of CDS
View for redirect
View to read the content of
The database table (WBO)
Redirect to compatibility
View)
View to read the
Master data
Attributes only
MKPF
Material
Document
Header
NSDM_DDL_MKPF
NSDM_MIG_MKPF
MSEG
Material
Document item
NSDM_DDL_MSEG
NSDM_MIG_MSEG
MARC
Plant Data for
Material
NSDM_DDL_MARC
NSDM_MIG_MARC
V_MARC_MD
MARD
Storage Location
Data for Material
NSDM_DDL_MARD
NSDM_MIG_MARD
V_MARD_MD
MCHB
Batch stocks
NSDM_DDL_MCHB
NSDM_MIG_MCHB
V_MCHB_MD
MKOL
Special Stocks
From Vendor
NSDM_DDL_MKOL
NSDM_MIG_MKOL
V_MKOL_MD
MSLB
Special Stocks
With Vendor
NSDM_DDL_MSLB
NSDM_MIG_MSLB
V_MSLB_MD
MSKA
Sales Order Stock
NSDM_DDL_MSKA
NSDM_MIG_MSKA
V_MSKA_MD
MSSA
Total Customer
Orders on Hand
NSDM_DDL_MSSA
NSDM_MIG_MSSA
MSPR
Project Stock
NSDM_DDL_MSPR
NSDM_MIG_MSPR
V_MSPR_MD
MSSL
Total Special
Stocks with
Vendor
NSDM_DDL_MSSL
NSDM_MIG_MSSL
MSSQ
Project Stock
Total
NSDM_DDL_MSSQ
NSDM_MIG_MSSQ
MSKU
Special Stocks
With Customer
NSDM_DDL_MSKA
NSDM_MIG_MSKU
V_MSKU_MD
MSTB
Stock in Transit
NSDM_DDL_MSTB
NSDM_MIG_MSTB
MSTE
Stock in Transit
To Sales and
Distribution
Document
NSDM_DDL_MSTE
NSDM_MIG_MSTE
MSTQ
Stock in Transit
For Project
NSDM_DDL_MSTQ
NSDM_MIG_MSTQ
MCSD
DIMP: Customer
Stock
NSDM_DDL_MCSD
NSDM_MIG_MCSD
MCSD_MD
MCSS
DIMP: Total
Customer Stock
NSDM_DDL_MCSS
NSDM_MIG_MCSS
MCSS_MD
MSCD
DIMP: Customer
Stock with
Vendor
NSDM_DDL_MSCD
NSDM_MIG_MSCD
MSCD_MD
MSCS
DIMP: Customer
Stock with
Vendor-Total
NSDM_DDL_MSCS
NSDM_MIG_MSCS
MSCS_MD
MSFD
DIMP: Sales
Order Stock with
Vendor
NSDM_DDL_MSFD
NSDM_MIG_MSFD
MSFD_MD
MSFS
DIMP: Sales
Order Stock with
Vendor-Total
NSDM_DDL_MFS
NSDM_MIG_MSFS
MSFS_MD
MSID
DIMP: Vendor
Stock with
Vendor
NSDM_DDL_MSID
NSDM_MIG_MSID
MSID_MD
MSIS
DIMP: Vendor
Stock with
Vendor-Total
NSDM_DDL_MSIS
NSDM_MIG_MSIS
MSIS_MD
MSRD
DIMP: Project
Stock with
Vendor
NSDM_DDL_MSRD
NSDM_MIG_MSRD
MSRD_MD
MSRS
DIMP: Project
Stock with
Vendor-Total
NSDM_DDL_MSRS
NSDM_MIG_MSRS
MSRS_MD
MARCH
History
NSDM_DDL_MARCH
NSDM_MIG_MARCH
MARDH
History
NSDM_DDL_MARDH
NSDM_MIG_MARDH
MCHBH
History
NSDM_DDL_MCHBH
NSDM_MIG_MCHBH
MKOLH
History
NSDM_DDL_MKOLH
NSDM_MIG_MKOLH
MSLBH
History
NSDM_DDL_MSLBH
NSDM_MIG_MSLBH
MSKAH
History
NSDM_DDL_MSKAH
NSDM_MIG_MSKAH
MSSAH
History
NSDM_DDL_MSSAH
NSDM_MIG_MSSAH
MSPRH
History
NSDM_DDL_MSPRH
NSDM_MIG_MSPRH
MSSQH
History
NSDM_DDL_MSSQH
NSDM_MIG_MSSQH
MSKUH
History
NSDM_DDL_MSKAH
NSDM_MIG_MSKAH
MSTBH
History
NSDM_DDL_MSTBH
NSDM_MIG_MSTBH
MSTEH
History
NSDM_DDL_MSTEH
NSDM_MIG_MSTEH
MSTQH
History
NSDM_DDL_MSTQH
NSDM_MIG_MSTQH
MCSDH
History
NSDM_DDL_MCSDH
NSDM_MIG_MCSDH
MCSSH
History
NSDM_DDL_MCSSH
NSDM_MIG_MCSSH
MSCDH
History
NSDM_DDL_MSCDH
NSDM_MIG_MSCDH
MSFDH
History
NSDM_DDL_MSFDH
NSDM_MIG_MSFDH
MSIDH
History
NSDM_DDL_MSIDH
NSDM_MIG_MSIDH
MSRDH
History
NSDM_DDL_MSRDH
NSDM_MIG_MSRDH
Https://blog.csdn.net/weixin_42137700/article/details/104339248
Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.
Views: 0
*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.
Continue with the installation of the previous hadoop.First, install zookooper1. Decompress zookoope
"Every 5-10 years, there's a rare product, a really special, very unusual product that's the most un
© 2024 shulou.com SLNews company. All rights reserved.