Procurement Workflow in terms of SAP Tables Changes

1. 1.Purchasing Request
2.Purchasing Order
EBAN(PR)
Purchasing Req (BANFN)
Item (BNFPO)
EKET(Delivery
Schedules)
Purchasing Doc (EBELN)
Item (EBELP)
Delivery Schedule (ETENR)
Vendor Info
EKKO(Purchasing
Document Header)
Purchasing Doc (EBELN)
LIFNR
Company Code(BUKRS)
3.Goods Receipt
4 Invoive
MARA Has
details about
the materials
which can be
raised for
procurement
LFA1 has
details about
each vendor
who supplies
us the items
to be
procured
EBAN is used
to store
Purchase
Requisition
information
EBKN
Purchase
Requisition
Account
Assignment
EKET is used
to store
Scheduling
Agreement
Schedule
Lines
information
The
header information
about the vendor and
the document
number is contained
in the EKKO
The material
description and the
order quantity are
specified in each item
which is stored in
EKPO
EKBE is used to
store History per
Purchasing
Document
information
RBKP is a standard
SAP Table which is
used to store
Document Header:
Invoice Receipt
information
RSEG is a
standard SAP
Table which is used
to store Document
Item: Incoming
Invoice information
BSAK is a standard
SAP Table which is
used to store
Accounting:
Secondary Index for
Vendors (Cleared
Items) information.
Accounting Post Procurement
Changes to a lot of
SAP documents are
stored in table
CDHDR and table
CDPOS. This include
changes such as:
change data in
Material Master,
changes to Purchase
Req (PR), Purch
Orders, Contracts,
Sales Orders, and
many more.
CDPOS is a standard
SAP Cluster table
which is used to store
Change document
items information
MARA(Material Master:
General Data)
Material No (MATNR)
EBKN(PR Account
Assignment)
Purchasing Req (BANFN)
Item (BNFPO)
PregAccountAssignment(ZEBKN)
EKPO(Purchasing
Document Item)
Purchasing Doc (EBELN)
Item (EBELP)
Material No (MATNR)
Purchasing Req (BANFN)
Item (BNFPO)
EKKN is a standard
SAP Table which is
used to store
Account Assignment
in Purchasing
Document
information.
EKKN(Account
Assignment in
PurchasingDocument)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assignment (ZEKKN)
EKBE((History of
Purchasing Document)
Purchasing Doc (EBELN)
Item (EBELP)
Account Assign (ZEKKN)
Trans Type (VGABE)
Fiscal Year (MJAHR)
Document No (MBLNR)
Line Item (ZEILE)
RBKP(Invoice received)
BELNR(Invoice no)
GJAHR
LIFNR
Company Code(BUKRS)
RSEG(Invoice Table)
BELNR
GJAHR
BELNR(Invoice no)
Purchasing Doc (EBELN)
Item (EBELP)
CDHDR
Purchasing Req (BANFN)
Changer
(Document change number)
BSAK
BELNR
LIFNR
CDPOS
Purchasing Req (BANFN)
Changer
(Document change number)
S2P SAP Data Flow
LFA1(Vendor Master)
LIFNR
Related SAP tables and Process Flow
EKKO (Purch Doc Hdr)
|
|
EKPO (Purch Doc Item)-------------EBAN (Req Item)
| |
| |
COOI (Commitmt Itm)----EKKN (Purch Doc Acct Asgmnt)------EBKN (Req Acct Asgmnt)
|
|
BKPF/BSEG (FI)---------EKBE (Purch Doc History)
|
|
PAYR (Payments)
1.Entering requisition creates EBAN & EBKN records.
2.Entering PO creates EKKO, EKPO, EKKN & COOI records.
3.Entering invoice against PO creates EKBE, BKPF & BSEG records.
Updates COOI records.
4.PO Changes - header changes can be detected through a type of audit
trail. The table CDHDR records changes to documents. The identifier
for POs seems to be CHange Doc Object = 'EINKBELEG'
Object Value = PO Number
DocNumber = Change document number
ChangeId = U/I/D (update, insert, delete)