Vbeln field in sap

Vbeln field in sap DEFAULT

Welcome Back :

ERP Genie - great site for SAP related content

SCN SAP Community Network, previously called the SAP Developer Network. Great place to read up on discussions on particular issues. This is were SAP consultants publish blogs, how-to's, and answer messages from SAP projects. On SCN, we have an article out on the

SAP Automotive Dealer Portal- a customer and dealer portal solution,- an important component of a end-to-end warranty solution. THe name Automotive Dealer Portal implies the solution is for the automotive industry. And that is correct, it initiated from the industry solution, and easily applicable to most other discrete industries, such as A&D, manufacturing, construction equipment. WebDynpro based, the Dealer Portal is running at several SAP customers. We helped several Dealer Portal projects go live.  

ECC Tables:

SAP Consultants configuring SAP Service, Maintenance and Warranty Management will be working in MM, PM/CS, SD, and FICO (FI/CO) modules.  

MM (Materials Management) MODULE

SAP Consultants configuring SAP Service, iMRO, MRO, Sales, and Warranty Management, etc., as well as specifying FRICE enhancements, will normally be dealing with these tables and key fields.

The Procurement Cycle consists of Purchase Requisition (PR), Request for Quotation (RFQ) (Vendor Evaluation), Purchase Order (PO) Goods Receipt Note (GRN), and Invoice Verification Data to FI.

Tables and Important Fields:

TableDescriptionKey Fields
LFA1Vendor DataLIFNR

Company Code Segment : Vendor Data

LFC1FI Related Vendor Data LIFNR, BELNR
LFM1Pur. Orgn. Related Vendor Data LIFNR, EKORG
MARAMaterial MasterMATNR
MARCMaterial Master with Plant Data MATNR, WERKS
MARDMaterial Master with Storage Location Data MATNR, LGORT, WERKS
MAKTMaterial Master Material DescriptionsMATNR, MATKL
MBEWMaterial Valuation Data MATNR, BWTAR
MVKEMaterial Master : Sales related 
MDKP, MDTBMRP Related Data Header 
MCHA, MCHBMaterial Batches Header, ItemMATNR, WERKS, LGORT, CHARG
EINA Purchase Info. RecordGeneral Data
EINE Purchase Info. Record pur. Orgn. Data
ELBK, ELBN, ELBP  Vendor Evaluation Related 
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
TF Confirmation Texts EBTYP, EBTXT
T Movement TypesBWARE
T Purchasing 
TE Purchase 
T Item Category’s in PurchasingPSTYP
TD Valuation 
T Material 
FVLK Delivery 
STKO, STPO BOM related Data 
KONO, KONH  Pricing 
T Basic Unit Of 



Sales cycle consists of: Enquiry, Quotation, Sales Order, Delivery (Picking, Packing, Post Goods Issue and Shipment), Invoicing, and Billing Data release to FI and CO.

TableDescriptionKey Fields
VBAK Sales Document HeaderVBELN
VTTK Shipment Table Header DataTKNUM
VTTP Shipment Table Item Data TKNUM, TPNUM, VBELN
VBRK Billing Table Header Data VBELN, FKART, BELNF
VBUK All Sales Documents status & Admn. Data header (VBELN,VBELN, VBTYP

VBTYP = ‘C’ (Sales Order) VBTYP = ‘L’(Delivery) VBTYP = ‘M’(Invoice)

VBUP Sales Documents status & Admin. Data(Item)VBELN
VBEP Sales Document Schedule Lines Data VBELN, POSNR, EDATU, WMENG
VBKD To get sales related Business data like Payment terms etc.VBELN
VBFA Sales Document flow dataVBELV, VBELN, POSNV, VBTYP
VBPA Partner functions DataVBELN, PARVW, KUNNR, LIFNR
TVLKT Delivery Type: TextsLFART, VTEXT
KNA1, KNB1, KNC1  Customer Master Data and Other Partner’s Data KUNNR, NAME1,LAND1
KNVK Customer Master Contact PersonPARNR, KUNNR
KNVV Customer Master Sales 
LFA1, LFB1, LFC1 Vendor Master Data(To get Transporter data)To get Transporter data
MARA, MARC, MARD Material Master DataBasic, Plant, St. Location Views
TVKOV DistributionVTWEG
TD Customer AccountKTOKD
TWLAD To get address of Storage Location and PlantLGORT, ADRNR
TVAU Sales Document (Order), Order TypesOrder Types
KONV Condition Types (pricing)  KNUMV, KSCHL, KWETR
TT Condition Types 
ADRC To get Addresses of 
VBBE, VBBS Sales Requirements 
VBKA Sales Activities 
VBPV Sales Document Product 


PP / PM / CS

SAP Consultants configuring SAP PP and or PM which is somewhat underlying the CS Customer Service module, as well as specifying FRICE enhancements, will normally be dealing with these tables and key fields. 

TableDescriptionKey Fields  
AFKO PP Order Header 
AFPO PP Order Item 
AFVV Order Operations Data 
AFVC Operations within an 
AFRU Order Completion 
CSLA Activity Types Master 
CSLT Activity Types 
KAKO Capacity Header 
CRHD Work Center Header 
AUFK Order Master 
AFIH Maintenance Order 
AUFMGoods Movement For 
EQUI Equipment Master 
EQKT Equipment 
ILOA PM Object 
TI Maintenance Planner 
T Plant 
IFLO Functional Location 
IHSG Permits in 
IHGNS Permit segment in 
TG_T Permit 
RESB Reservation / Dependent 
V_EQUI View for Equipment 
VIAUFKS View for Order and Equipment 
CAVFVD Work Center 
VIQMEL Notification Header 
VIQMFEL PM Notification 
VIQMMA, VIQMSM  Views for Activities and 


Master Warranty Tables (CS / PM)

SAP Consultants configuring service/maintenance and warranty modules PM, CS, and LO-WTY, as well as specifying FRICE enhancements, will normally be dealing with these tables and key fields: 

TableDescriptionKey Fields
BGMK Master Warranty Header 
BGMT Master Warranty Text 
BGMS Master Warranty Position 
BGMZ Master Warranty Position Counter 


FI / CO (Finance)

SAP Consultants configuring finance modules FI and CO, as well as specifying FRICE enhancements, will normally be dealing with these tables and key fields: 


TableDescriptionKey Fields
T Company 
T Language 
T FI Document 
T Chart Of 
T Country 
TA Tax 
T House 
TKA01 Controlling 
SKA1, SKB1 G/L Account Master 
SKAT  G/L Accounts 
KNBK Customer Master(BankBank Details
LFBK Vendor Master (BankBank Details
BKPF Accounting Doc. 
BSEG Accounting Doc. Item(ClusterCluster Table
BSIS G/L Open 
BSAS G/L Closed 
BSID Customer Open Items (Account Receivables)Account Receivables
BSAD Customer Closed Items (Account Receivables) 
BSIK Vendor Open Items (Accounts Payable)Account Payables
BSAK Vendor Closed Items(AccountAccount Payables
BKPF and BSEG BKPF and BSEG Tables consists of data from BSIS, BSAS, BSID, BSAD, BSIK, and BSAK tables. 
BSEC One Time Vendor 
CSKS Cost Center 
CSKT Cost Center 
CSSK Cost Center/ Cost Element 
GLPCA EC-PCA: Actual Line 
COEP Co-Object Line Items by 
COST Co-Object Price 
CSSL Cost Center- Activity 
CRCO Work Center- Cost Center 
CSLA Activity TypesLSTAR
COBL Coding 
CEPC Profit Center Master 
BNKA Master Records of 
TBSL Posting 
KEKO Product Costing Header 
ANLH Main Asset 
ANLA, ANLB, ANLC Segment Assets Masters 


Have more complex SAP Service (MRO), Sales, and Warranty configuration requirements? 

Then our team of experts is available. All you have to do to take advantage of it is to press the button below and request your initial and pro-bono consultation:

Request an Initial FREE Consultation

Sours: https://www.deteringconsulting.com/sap-ecc-tables-related-resources-web-sites

Boomi SAP series: guide to read SAP table data in Boomi

Greetings fellow BoomiSAPians.
I will start my SAP article series with how to utilize SAP TABLE data in Boomi. As you know, SAP data is mostly stored in tables in the SAP system. So as an integration specialist you will often face the challenge in how to get to that data. This article explains how to do that without any ABAP or JAVA code at all.Just by leveraging Boomi's second to none iPaaS.
Eventually what we will end up with is a process like this:
RFC_READ_TABLE process complete
  1. Boomi account (surprise!)
  2. The Boomi SAP Enterprise connector (help link) (so minimum an Enterprise account or added Enterprise connectors)
  3. An SAP system (see above link for supported SAP versions)
  4. Coffee
One other approach could be to build a custom BAPI or remote enabled function module (RFM) in SAP. This should read the data and serve the data up in a format matching the exact requirements. This is all good but by developing an RFM you also introduce ABAP code that needs to be documented, QA’ed and maintained through multiple SAP upgrades. So, you get what you want but also you are introducing more work since you are injecting custom code into your SAP system that must be maintained and governed. Can you see how the LOW TCO incentive is starting to drip down the drain?
So lets stick to Boomi now that we can. Well, SAP is way ahead of you. Back in the 's SAP build a RFM or BAPI that you can leverage. In your SAP ECC system you will find a remote enabled function module (we can call it a BAPI) RFC_READ_TABLE. With this BAPI (or Remote enabled function module) you can access almost any SAP table data you desire using the Boomi SAP connector. It does have some limitations but let’s touch on that later (see below on notes on RFC_READ_TABLE)
  1. First you need to import the REQUEST and the RESPONSE profiles for the RFC_READ_TABLE function.
  2. Next you will have to populate the REQUEST profile to be prepared for the selection of the data
  3. Finally you need to read the RESPONSE from SAP and learn how to interpret that.
All the above is pretty standard when you work with Boomi connectors, but let's make sure we get all on the same page. Step 2 is simple but you can be very clever in this step and you can here specify some access techniques to the SAP table data that can save you a lot of time. So stay tuned folks!

Use case description

Select order item data from SAP based on a single order number, select all items for that order number and transform the data to XML to send to your integration endpoint of choice.
SAP table to be used is VBAP (order item data). Yes you could use a BAPI for this but sometimes it is easier and faster to access the data directly from the source.

How to pick the right SAP table fields

You need to investigate the SAP table fields in order to choose which fields to work with, so which fields is required. Lets investigate how to get to the table data and secondly how to find out which fields to pick (what is the FIELDNAMES).
Go in to SAP and call transaction SE16(table content browser in SAP)

SE16 hint
You can select whether you want to see FIELD NAMES or FIELD LABELS in the SE16 LIST.
Select Settings/User Parameters and select your choice. When working with RFC_READ_TABLE we need to use the Field names but for investigation purposes and field explanation use Field labels to start and Field names when you are ready to pick your fields.
SE16 tips. How to specify which tablefield keywords to display

Looking at the table view in SE16 we see similar output as below (here Field name is set to be displayed)
SE16 table view of VBAP

Fields identified

By looking through the list I identified the following fields: (scroll right in SAP to see all the fields)
VBELN (order number)
POSNR (Order item)
MATNR (material number)
ARKTX (Material text)
KBMENG (cumulative confirmed quantity)
MEINS (Unit of measure)
NETWR (Net value of orderline)
WAERK (Currency code sold)

Those are fields that is required for my use case. 

Let’s jump in to Boomi and start building.

Import profiles from SAP

First of all you need to import the profiles for RFC_READ_TABLE, so assuming you have your SAP connector set up you have to import it in the Operation part. Click IMPORT, select BAPI/RFM and specify RFC_READ_TABLE
SAP import RFC_READ_TABLE profiles
With that safely imported lets talk about the strange looking REQUEST profile and talk through some of the fields

Demystifying the REQUEST profile for RFC_READ_TABLE

The request profile looks like this, I have added some "wise words" on the data elements in the profile
RFC_READ_TABLE request explanations
NO_DATA: Mark this with an ‘X’ and it will return only the enriched fields (name, type etc) and NO DATA
ROWSKIPS: how many ROWS should be skipped

NOTE: The OPTIONS/item/TEXT follows the rule for the ABAP statement SELECT WHERE so you if you have ABAP skills you can tailor this in to a pretty detailed level combining multiple fields with multiple operands like AND and OR. Have a look in the ABAP code documentation and let the creativity start.
Not all can be used but have a go with it.
A link to the SAP ABAP documentation can be found here

A screen "snippet"

Prepping your REQUEST profile

There are many ways to "prep" your REQUEST profile, you could use a MESSAGE shape and then enrich the profile with the required parameters using variables in placeholders or you can use a MAP shape. For learning purposes, I will use a MAP shape. But being a hardcore BoomiSAPian I normally use a MESSAGE shape. Here I copy in the REQUEST and then adding nodes to the XML as required (new fields, options in placeholders etc etc)

Anyway, let’s look at my initial mapping:

Source profile

You see how my source profile is just a flat-file profile. The field I use for this article is VBELN or order number and for the sake of the example I will pass in the data using a MESSAGE shape with the value of the order number. You can implement this as you desire and to your exact requirements.

Target profile

On the target side of the mapping shape I have used position based instance identifiers (link) to add the fields identified above and the rest of the required input like delimiter, table name, row count etc. 
Note on instance identifiers: I use "Identify By Occurrence" - so create one instance for each field. We got 8 fields, so I added 8 occurrences on the level of FIELDS/item.
Remember this is just ONE way to do this. It serves as an example and if you are new to Boomi you might learn some new tricks.
Identifier instance RFC_READ_TABLE


You will also notice that I have added a custom function and to that, added a concatenate function. A single function could be used but we might extend this later so hence the choice of custom function. 
The concatenate function serves to build up the statement for the selection so like VBELN EQ ‘{v}’
{v}being the variable from the source profile.
So after a successful mapping into the REQUEST profile you can now execute the SAP connector shape which will return the data from the SAP system into the RESPONSE profile of RFC_READ_TABLE. 
So lets look at that RESPONSE profile.

Demystifying the RESPONSE profile

Demystifying the RFC_READ_TABLE RESPONSE profile
What you will see when executing the process, is that SAP has kindly returned your data in the RESPONSE profile. 
All the fields chosen has now been enrich with information like field label, field lengthetc. you can use this if you would have to use the fields in a for example a report. The actual data is served in the WA field.
So looking at the WA content - it looks messy. But really SAP has returned the data you requested in a delimitted form that is easily processed using A String Split function in a mapping shape.

How to split the found data from DATA/item/WA?

We introduce a new mapping shape. Mapping the RESPONSE profile to a new XML target profile, ready to be send out to the required target systems.
RESPONSE mapping
As you can see, I added a String Split function in our mapping shape to split the data on the chosen delimiter ";" and added output fields for all required fields.
The target profile is a simple XML structure where all the fields I required are entered
Target XML profile
This is just the fields I chose to use, you canl have other fields in your target. It might be a database or API REQUEST profile for an API to a DATALAKE. Everything is possible in Boomi.
But anyhow, now the output from the mapping shape serves up the found SAP TABLE data in a nice XML format. This can now be ingested into the target system of your choice.

The final integration process

RFC_READ_TABLE process complete

The Test data MESSAGE shape

Here we can supply test data in the form of order numbers to be read in SAP. One order number per line.
Message shape
Again this is just an example, the order number might as well be passed in as a parameter in an API, so the process can be easily extended to become an API by adding the RETURN DOCUMENT shape to the end (replace STOP shape) and changing the START message to the Web Service Server connector, configure it and import the process into the API component as a REST, SOAP or Odata endpoint. And you got an API.
Easy peasy with Boomi.

Sample of XML RESPONSE data

For your information I have added a sample of the response from SAP so you can investigate this at your own leisure. Ordernumber (REMEMBER the prefixed zeroes when working with SAP!!) <?xml version="" encoding="UTF-8" standalone="no"?> <RFC_READ_TABLE> <DATA> <item> <WA>;;M ;Sunny Sunny 01 ; ;ST ; ;DEM</WA> </item> <item> <WA>;;M ;Sunny Xa1 ; ;ST ; ;DEM</WA> </item> <item> <WA>;;M ;Sunny Tetral3 ; ;ST ; ;DEM</WA> </item> <item> <WA>;;M ;Sunny Extrem ; ;ST ;

Example of the data after the mapping to the XML profile

<?xml version='' encoding='UTF-8'?> <XMLRootHead>   <Record>     <VBELN></VBELN>     <POSNR></POSNR>     <MATNR>M</MATNR>     <ARKTX>Sunny Sunny 01</ARKTX>     <KBMENG></KBMENG>     <MEINS>ST</MEINS>     <NETWR></NETWR>     <WAERK>DEM</WAERK>   </Record>   <Record>     <VBELN></VBELN>     <POSNR></POSNR>     <MATNR>M</MATNR>     <ARKTX>Sunny Xa1</ARKTX>     <KBMENG></KBMENG>     <MEINS>ST</MEINS>     <NETWR></NETWR>     <WAERK>DEM</WAERK>   </Record>   <Record>     <VBELN></VBELN>     <POSNR></POSNR>     <MATNR>M</MATNR>     <ARKTX>Sunny Tetral3</ARKTX>     <KBMENG></KBMENG>     <MEINS>ST</MEINS>     <NETWR></NETWR>     <WAERK>DEM</WAERK>   </Record>   <Record>     <VBELN></VBELN>     <POSNR></POSNR>     <MATNR>M</MATNR>     <ARKTX>Sunny Extrem</ARKTX>     <KBMENG></KBMENG>     <MEINS>ST</MEINS>     <NETWR></NETWR>     <WAERK>DEM</WAERK>   </Record> </XMLRootHead>
Finally lets wrap it up with some NOTES


Maximum row size

The maximum size in chars of the data element DATA/item/WA is chars. Dictated by SAP. (this could be extended if you created your own RFM in SAP ABAP - just copying the functionality from RFC_READ_TABLE in to your own eg. ZRFC_READ_TABLE)
Max size of WA

Optimizing reads on the table

Be conscious when designing your selection fields (OPTIONS/items/TEXT) that you use some of the key fields in the table.  For locating key fields, look in SE16 for the specific table in SAP. If you require fields that are not part of the key or in any of the alternative indexes of that table (SE11), go and have a chat with your SAP BASIS team to ask for an alternative index to be created. This is especially important if you are using tables that has many rows of data. But ask the basis team they will help you if it is required. Alternative indexes takes space so be prepared to explain your use case in details with the SAP BASIS team (the SAP technical team)


Alternatives: BBR_RFC_READ_TABLE. This one is basically the same. It has the same limitation on chars on WA but has option to use DISTINCT on selects but I find no references to the SELECT DISTINCT in the ABAP code, so I see no reason to use this compared to RFC_READ_TABLE. There are others, but I always tend to use RFC_READ_TABLE.

Wrap up

Thanks for your time to read my article. If you have any technical questions on this article or other SAP related questions, please use the community. If any questions on how to become a Boomi customer go and visit www.boomi.comand contact a Boomi representative here.
Happy SAPing with Boomi.

Bo Harreby Moller, Boomi Advisory Systems Engineer and SAP solution architect

Sours: https://community.boomi.com/s/article/Boomi-SAP-series-guide-to-read-SAP-table-data-in-Boomi
  1. Bingo zoom background
  2. Oneplus phone on verizon
  3. Neurology made ridiculously simple
  4. Ebt balance ny

New to Qlik Sense

Hello All,

I'm trying to only load data where VBLEN is equal to or more than   I have listed below the different things I have tried but none of these have worked and I am lost for ideas.

Any help will be hugely appreciated


What i've tried:

1.  Num(VBELN) as [Sales Order], 

      where VBELN >=

2. Same as above but with NUM# 

3. WildMatch(VBLEN, ' ******* ') 

4. WildMatch(VBLEN, ' ??????? ')

5. Num(Evaluate(VBELN) as [Sales Order] 


Full Code: 

Num(VBELN)) as [Sales Order],
POSNR as [Sales Item Number],
ETENR as [Delivery Schedule Line Number],
EDATU as [Delivery Date],
WMENG as [Order Quantity]

EDATU >= month(today())

Sours: https://community.qlik.com/t5/New-to-Qlik-Sense/how-to-filter-on-sap-field-VBELN-in-load-statement/td-p/

Read SAP Note before developing new SD report or if your SD report is running slow.

1. Accesses to sales orders (tables VBAK, VBAP)

Search orders for customer number (field VBAK-KUNNR)
If you want to look for sales order for a customer do not directly select from VBAK, instead first select on VAKPA and then based on what sales order you get execute second select in VBAK to get additional data.

IncorrectSELECT FROM vbak WHERE kunnr = &#;
CorrectSELECT FROM vakpa WHERE kunde = &#;
SELECT FROM vbak WHERE vbeln = vakpa-vbeln.

Search order items for material number (field VBAP-MATNR)
To search for sales order line for particular material select from table VAPMA first and then go to VBAP table for more information.

IncorrectSELECT FROM vbap WHERE matnr = &#;
CorrectSELECT FROM vapma WHERE matnr = &#;

SELECT FROM vbap WHERE vbeln = vapma-vbeln
AND posnr = vapma-posnr

Use search help views defined for Sales Order
Other search helps for sales orders offer the matchcode tables and views M_VMVAx, x. = A, B, C, &#; M; for example search for purchase order number of the customer, description and so on.

View NameSearch Fields
M_VMVAACustomer PO number
M_VMVAEPartner number (KUNNR, LIFNR, or PERNR)
M_VMVALSales Org, Sold-to party
M_VMVAOSold-to party

2. Accesses to deliveries (tables LIKP, LIPS)

Search for deliveries with customer number (field LIKP-KUNNR)

IncorrectSELECT FROM likp WHERE kunnr = &#;
CorrectSELECT FROM vlkpa WHERE kunde = &#;

SELECT FROM likp WHERE vbeln = vlkpa-vbeln.

Search for delivery items with material number (field LIKP-MATNR)

IncorrectSELECT FROM lips WHERE matnr = &#;
CorrectSELECT FROM vlpma WHERE matnr = &#;

SELECT FROM lips WHERE vbeln = vlpma-vbeln
AND posnr = vlpma-posnr

Search for deliveries with sales order number (preceding document, field LIPS-VGBEL)

IncorrectSELECT FROM lips WHERE vgbel = &#;
CorrectSELECT FROM vbfa WHERE VBELV = &#; and VBTYP_N = &#;J&#;

SELECT FROM lips WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

Use search help views defined for Delivery
Other search helps for deliveries offer matchcode tables and views M_VMVLx, x. = A, B, C, &#; M; for example search for goods issue date, picking date, transportation planning date and so on.

3. Accesses to invoices (tables VBRK, VBRP)

Search for invoices with customer number (&#;payer&#;) (field VBRK-KUNRG)

IncorrectSELECT FROM vbrk WHERE kunrg = &#;
CorrectSELECT FROM vrkpa WHERE kunde = &#;

SELECT FROM vbrk WHERE vbeln = vrkpa-vbeln

Search for invoice items with material number (field VBRP-MATNR)

IncorrectSELECT FROM vbrp WHERE matnr = &#;
CorrectSELECT FROM vrpma WHERE matnr = &#;

SELECT FROM vbrp WHERE vbeln = vrpma-vbeln
AND posnr = vrpma-posnr

Search for invoices with delivery number (preceding document, field VBRP-VGBEL)

IncorrectSELECT FROM vbrp WHERE vgbel = &#;
CorrectSELECT FROM vbfa WHERE vbtyp_n = &#;M&#; AND vbelv = &#;
SELECT FROM vbrp WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

Search for invoices with order number (preceding document, field VBRP-AUBEL)

IncorrectSELECT FROM vbrp WHERE aubel = &#;
CorrectSELECT FROM vbfa WHERE vbtyp_n = &#;M&#; AND vbelv = &#;
SELECT FROM vbrp WHERE vbeln = vbfa-vbeln
AND posnr = vbfa-posnn

4. Other accesses in SD

Document flow
In table VBFA only the preceeding document is used to search for the subsequent document (for example, delivery for order). Searching the other way makes no sense with this table since the preceding documents (for example, order for delivery) are stored directly in the document tables. Thus reading in table VBFA is a one-way street.

IncorrectSELECT vbelv FROM vbfa WHERE vbeln &#;
CorrectSELECT vgbel FROM lips WHERE vbeln = &#;;
SELECT vgbel FROM vbrp WHERE vbeln = &#;;
SELECT aubel FROM vbrp WHERE vbeln = &#;

Search for shipping unit item with delivery

IncorrectSELECT FROM vepo WHERE vbtyp = &#;J&#; AND vbeln = i_lips-vbeln
CorrectSELECT FROM vbfa WHERE vbtyp_n = &#;X&#;
AND vbelv = i_lips-vbeln
SELECT FROM vepo WHERE venum = vbfa-vbeln

Link to SAP Note

Sours: https://www.samplecodeabap.com/sd-table-access/

In vbeln sap field

SAP VBELN (Sales and Distribution Document Number) Data element field

ASD Document/MaterialASD Document/Item/MaterialASD Document/Item/Material Pricing GroupASD Document/ItemAACRN ID/Material/Version Number/PriorityAMaterial/Agreement Data for ATO/MTS ComponentsAAgreement Data and status with agreement searchASD doc./Item/CustomerASD doc./Item/Material/CompMat/CompSup/CompTypeASD doc./Item/Customer/PersonnelASD Doc./Customer/PersonnelASD Doc./Item/Personnel/Sold-to pt/No.ser.no./CustomerASales org./Distr. chl/Customer/Material/DRM Agr No/DRM ItmAAgreement data in combination with Agreement searchAMaterial/Customer/Agreement dataAMaterial/Agreement dataACCTITCompressed Data from FI/CO DocumentAFKOOrder Header Data PP OrdersARCID_P_VBRKArchiving SD_VBRK: Index table (primary)ARCID_S_VBRKArchiving SD_VBRK: Index table (secondary)ARCID_VBRKArchiving SD_VBRK: Index TableBAD_CUBINBAD - Configuration ValuesBAD_CUCFGBAD - Configuration Data IDsBAD_CUCHARTXTBAD - Configuration ValuesBAD_CUINSBAD - Instance of ConfigurationBAD_CUPRTBAD - Item: Part of dataBAD_CUVALBAD - Configuration ValuesBAD_CUVALTXTBAD - Configuration ValuesBAD_CUVARCBAD - Variant ConditionBBP_PCLOGProcurement Card Statement: Logistic dataBBP_PDCONPurchase Order Item ConfirmationBBP_SDDOC_FAVUser-Specific Favorites for Permitted Customer OrdersBLPKDocument log headerCEERRORCO-PA: Incorrect records from SDCHBSMWBWeb related info to modelsCIFSLSMAPMapping Table NR/POS/ET <-> APO GUID (Sales Orders)CIF_IMMSKAIntegration Model Reference Table for Sales Order StockCKMLHDMaterial Ledger: Header RecordCKMLHD_AGGRMaterial Ledger: Header RecordCKMLMVProcurement alternativesCKMLMV_AUX_KALNRCost Estimate Numbers for Valuated Objects in QSTCKMVFM_BSEG_OUTDisplay of FI Documents, Transaction CKMVFM, SAP Note CKMVFM_OUTOutput for the Value_Flow_Monitor, see SAP Note CMPB_ASGNCampaign AssignmentCMP_VBFS_EXTStatus Messages from Mass Complaints ProcessingCNVCMIS_M_VMVLACMIS: Temp. Generated Structure for MC-IdCNVCMIS_M_VMVLBCMIS: Generated Pooltable for Matchcode ID VMVL -BCNVCMIS_M_VMVLCCMIS: Temp. Generated Structure for MC-IdCNVCMIS_M_VMVLDCMIS: Generated Pooltable for Matchcode ID VMVL -DCNVCMIS_M_VMVLICMIS: Generated Pooltable for Matchcode ID VMVL -ICNVCMIS_M_VMVMACMIS: Generated Pooltable for Matchcode Id VMVM-ACNVCMIS_M_VMVMDCMIS: Generated Pooltable for Matchcode ID VMVM -DCNV__VBELNSales documents selected for deletionCOERSales Order Value RevenueCOPA_CRMSTATUSCO-PA Status: Records from CRMDGMS2DG: Dangerous Goods Document Table (Appendix Table)DGMSDDG: Dangerous Goods Document Table DGMSDDIPCS_SDRULESSpecific Stock determination rules for customerEBEWSales Order Stock ValuationEBEWHValuation of Sales Order Stock: HistoryEBKNPurchase Requisition Account AssignmentEEWA_BULK_DATABulk refuse order dataEEWA_GUARANTORGuarantor ContractEIEIForeign Trade: Export/Import Communication DataEIKPForeign Trade: Export/Import Header DataEIUVForeign Trade: Incompletion Log for Foreign Trade DataEKKNAccount Assignment in Purchasing DocumentESKNAccount Assignment in Service PackageESLHService Package Header DataEVERIS-U Cont.EWA_WA_PCKGDSREGGeneral Cargo EntryEWA_WA_WEIGHPROCWeighing ProcedureFAGL_R_SDLOG_Reorganization: Log of Non-Reorganized Sales DocumentsFCML_MATML Characteristics for Material (Selection Criteria)FDS1Cash Management & Forecast: Line Items of SD DocumentsFIEUD_SDINV_HSAFT: Invoices from SD module(Header)FIEUD_SDINV_ISAFT: Invoices from SD module(Item)FKK_KONV_SHORTPrice Conditions for SD Billing Document - ExtractsFKK_VBPA_SHORTPartner Data for SD Billing Document - ExtractsFKK_VBRK_SHORTHeader Data for SD Billing Document - ExtractsFPLABilling PlanFPLAPOBilling PlanFSLSIForeign Trade: Legal Control - Sanct. Party List - IndicesFSLSTForeign Trade: Legal Control - SLS - Audit TrailFSLSTAForeign Trade: Legal Control - SLS - Audit TrailFTGKLLegal Control: Log (Up-to-Date)FTGKLALegal Control: Log (Prestep for Archiving)GLE_FI_ITEM_MODFECS: Modified FI Line Items (Header/Item/Currency Data)GLE_FI_ITEM_ORIGECS: Original FI Line Items (Header/Line Item/Crcy Actg I/F)GLPCAEC-PCA: Actual Line ItemsGLPCA_CTProfit Center DocumentsGLSPCProfit Center Accounting: Line ItemsIDGT_GTDMMapping of SAP Document and GT DocumentIDGT_INFOGTI China: Data sent to GTIPM_RAWRECDue Pre-List for Product SalesISAUTOEKLWESLast Deliveries for FLABJFXBELEGDLIS-M: Backup Transfer Internal Table XBELEGJFXBELPODLIS-M: Backup Transfer Internal Table XBELPOJKA51_VBAPAppend to Z51JKSDCONTRACTQUANIS-M: Contract-Related QuantitiesJKSDDEMANDFLOWIS-M: Assignment of Contract Item to OrderJKSDGENRESTARTIS-M: Restart Log for Order GenerationJKSDLOGORDERSTIS-M: Status QueryJKSDORDERGENIS-M: Internal Control Table for Order GenerationJKSDORDERINDEXIndex Table for IS-M OrdersJKSDORDERQIS-M: Order QuantitiesJKSDPLANQEVENTEXIS-M: Use of EventJKSDPROTOCOLIS-M: Order Generation LogJKSDQEVENTVERIFYIS-M: Verified Planned Quantity (Event Planning)JKSDQFASCONIS-M: Assignment Area - Segment - ContractJKSDQUANTITYROLEIS-M: Contract-Related Quantities for Specific RolesJKSDQUANUPDMSDIS-M: Updated Deliveries in Shipping OrdersJKSDQUANVERIFYIS-M: Verified QuantitiesJKSDREQ_ORDPLANTIS-M/SD: Request Table for Plant Change in OrdersJKSDREQ_ORDSHIPPIS-M/SD: Requirements Table for Shipping Point ChangeJKSDSCHEDERRError Log on Changes to Schedule Line DataJKSDSCHEDERRTABError Log on Changes to Schedule Line DataJKSDTRANSFERCOMIS-M: Table with Comment on JKSDTRANSFERJKSDUNSOLDCOMIS-M: Table with Comment on JKSDUNSOLDJKSDWWWERROR01IS-M: Error Records for Retail via InternetJKSD_KNVP_CONTRIS-M: Time-Dependent Partner Roles in MPS - ContractsJKSECONTRINDEXIS-M: Index Table for IS-M ContractsJKSEFLOWIS-M: Document Flow for Generated Orders ISPJKSEGENRESTARTIS-M: Restart Log for Order GenerationJKSEINTERRUPTIS-M: SuspensionsJKSEORDERGENOBSOLETE - IS-M: Internal Control Table for Order GenerationJKSESCHEDIS-M: Media Schedule LinesJKSESUBPRICESETPIS-M: Contract - Discount GroupJPTRAWRECDue Pre-List for Product SalesJVSDCONTRACTLFNGIS-M: Subscription Deliveries for Contract and Media IssueJVTNOTADMIS-M/SD: Administrative Data on Carrier Change NotificationJ_1IFRDTSOTransaction table for Forms Tracking for Sales.J_1SMWSNWSIS-M/SD CH/F: VAT Statement for VAT Deduction by AgreementKALMCosting Run: Costing ObjectsKALOCosting Run: Costing Objects (KVMK)KANZAssignment of Sales Order Items - Costing ObjectsKEKOProduct Costing - Header DataKOTFSD Document/ItemLEDSPD_FLOWDocument Flow for Subsequent Outbound-Delivery SplitLTAKWM transfer order headerMC12_PUFFERInterim Buffering for MC12 Deltas?MCVSRFKStatistically Relevant Fields for Order + Delivery HeaderMCVSRFPStatistically Relevant Fields for Order + Billing DocumentMEIKMake-to-Order Stock for Customer OrderMLITMaterial Ledger Document: ItemsMMINKON_UPCorrections due to Technical Problems with StockMSCASales Orders on Hand with VendorMSCAHSales Order Stock at Vendor: HistoryMSFDSales Order Stock with VendorMSFDHSales Order Stock at Vendor: HistoryMSFSSales Order Stock with Vendor - TotalMSKASales Order StockMSKAHSales Order Stock: HistoryMSKAHO1MSKAH: Additional quantities appendixMSKAO1Special Stocks Appendix: Additional QuantitiesMSOATotal Sales Orders on Hand with VendorMSSATotal Customer Orders on HandMSSAHTotal Sales Order Stocks: HistoryMSTEStock in Transit to Sales and Distribution DocumentMSTEHSiT to Sales and Distribution Document - HistoryMWXVM07MFields: Update Control of Module Pool SAPMM07MMWZVM07MFields: Update Control of Module Pool SAPMM07MNREPIS-H: Items Collective Invoice SelectionNWCHLCOEAIS-HCO: ÃœberleitungsinformationenOIA05Quantity schedule scheduling table - sales sideOIA05HQuantity schedule header table - sales sideOIB08Log for HIM Quantities out of sync with SKUOICINT_MASTERInterest master dataOIC_FORM_ATTRIBAttributes of Business Context for F&A FormulaOIFPBLIndex to point at Business LocationOIGSPAPartner in TD-shipmentOIHLOUsed licenses for ordersOIJ_EL_DOC_EVRules for nomination eventsOIJ_EL_DOC_H_REFOil TSW: Document header reference to nomination; not usedOIJ_EL_DOC_I_REFDocument item reference to nominationOIJ_EL_DOC_MOTOil TSW: TSW Relevance of order itemOIJ_EL_DOC_M_MOTOIL TSW: TSW Details / Multiple MoT'sOIJ_SIM_SCHEDobsolete table (will be cleaned up)OIK37IS OIL: Shadow table for SD document processingOIKSSLTPI: Log tableOIRADTLTDocument transaction link tablePAYSP_HLPayment Service Provider DataPKPSControl Cycle Item / KanbanPRSD_CO_MAPPINGEM: Mapping original DMR lines to Carry Over linesPRSD_DMRP_ACC_CHEngagement Mgmt: Accrual Characteristics for DMR LinesPRSD_DMRP_EXTExtended DMR Line InformationPRSD_GRPGrouping, Sorting values for DLIPRSD_VBAK_EXTEngagement mgmt: Extended DMR Head InformationPVINXIndex of New Sales Documents for Product ProposalRBCODocument Item, Incoming Invoice, Account AssignmentRBSELDELIIncoming Invoice: Delivery SelectionREQACCTAccount Assignment for the Req. Coverage Request LinesRJFENQLock Object for Billing/Coll.Processing Generic/ExclusiveSCommunications Table SD -> CO/ProjectsSCAS: Last Documents
Sours: https://sapstack.com/tables/dataelements.php?field=VBELN
Lecture 05: ABAP Statements \u0026 Field Symbols - SAP ABAP Programming in a Nutshell - Ana Lekic SAP

Tears appeared in my eyes and, sobbing, I began to answer the girls' questions. I played cards for desire and lost. And the desire was such that I drove in this form between two adjacent stops.

Now discussing:

The drill is working again. Wait, "the speaker commanded, which gave the girl a break before the next execution. This is not the scream that I need, but I know what will truly make this trashy bitch squeal.

4618 4619 4620 4621 4622