Delveries in stages in shipment.

Hi All,
Which is the best table to get the deliveries in stages in shipment.
I know this can be fetched from VTTS or VTSP tables.But when the delveries sequence is changed ti should get correct details as per the stop.
awaiting for your help,
Thanks
Vivek

Hi.
We will get detials for stops in VTTS. VTTK & VTTP will only give detials about shipment.
I know TSRFO/TSNUM -VTTScan be used to to get the details.
But if there stop-3 delivereis are changed to stop-2 , there the problem comes.
So i have to get the delveries in the stage as per the their stop even if their stop changed i need to get exact stop where they are going to be delivered.
thanks
vivek

Similar Messages

Deliveries not assigned to stages in shipment

Hi,
For the outbound deliveries,Shipments will create via batchjob ( VT04-). After creating shipments, the DN's should assign to each stage in shipment document. But it is not assigned to the all stages. ( we have 4 stages in route & DN is assigned to only 3 stages but not for 4th stage )
can you please through some light on this? why its behaving like this?
what is the logic at the time of the leg determination?
-*All replies rewarded.

Dear RMD
May be this link will be of helpful to you.
http://help.sap.com/saphelp_47x200/helpdata/en/93/743f27546011d1a7020000e829fd11/frameset.htm
Thanks
G. Lakshmipathi

Stages for shipment cost Document

Hi,
I have three vendors(service Agent) involved for a leg such as forwarding agent, transporter and broker. Our company is dealing separately with each vendors.
how to handle this scenario. Kindly give the step to create stages. I have created stages but its not configured correctly.
Is it possible to have different pricing procedure for a service or can we handle in one pricing procedure?
Since I am new to shipment asking this question? If this is simple question kindly guide me to achieve it?
Waiting for you reply.
Regards
Fazal

Why isn't it configured correctly? you have to create item categories for each vendor type. For each vendor type you need one for the header of the transport and one for the legs.
Then for each item category you can define a pricing procedure.

How do deliveries get added to a stage in shipment

I am trying to configure automatic determination of stages for deliveries in the shipment legs
But every time all deliveries at all stages remain in one stage and then I have to move them manually or sometimes even that is not possible
I must be doing something wrong
Any ideas / tips from Gurus out there

hi,
Check out what you are missing in the steps you had followed from the standard procedure and also check the pre-requisites of automatic determination.
Prerequisites
This algorithm is triggered automatically in the following circumstances:
When a route is entered in the shipment header
After you carry out leg determination with category 0 to 4 (leg determination category 0 initiates the assignment determination process only).
Procedure
Assignment determination is carried out as follows:
The system analyzes the point of departure and destination for each delivery, one after the other (see also step 2 in Automatic Leg Determination.
If the point of departure of this delivery is found among the departure points of the existing legs and the destination is found among existing destinations, the system then looks for the legs that connect these two locations.
If the legs are incomplete (that is, if there are gaps between them), the delivery is assigned to all legs that start at the beginning point and also to all those that end at the destination.
If only the departure point exists in the system, the system assigns all adjoining legs to the delivery.
If only the destination exists in the system, all adjoining legs are assigned to the delivery (in other words, similar to step 3, only backwards).
If neither the departure point nor the destination exists in the system and if the delivery is a preliminary leg shipment or subsequent leg shipment, it is assigned to all legs. All other shipments with no departure point or destination in the system are only assigned to main legs. If this does not work either (because the leg indicator is not maintained, for instance), the deliveries are assigned to all legs that were created manually.
Now the system assigns the deliveries to border crossing points and load transfer points. The system then also checks which legs start or end at border point G, for example. All deliveries that are found in these legs are assigned to this border crossing point, since all deliveries that are shipped to this border crossing point must most likely go through customs.
Only deliveries that are to be loaded or unloaded at this point or those whose shipping type or service agent changes (meaning that they must be transferred) are assigned to a load transfer point.
If there are no legs that begin or end at this point, the system assigns all deliveries to this point.
regards,
Siddharth.

Stage in Shipment

Hi Transportation gurus,
We have a requirement to have one stage per one delivery within a Shipment document.
We combine multiple deliveries into one shipment and though the shipment leg is same across deliveries, our business wanted the shipment document to have individual stage for each delivery. This is because when we create Shipment Cost document we wanted the Shipment Cost item to represent single delivery.
Any thoughts/help highly appreciated.
Thanks

Hi SG,
Can you be more clear with your ?
Correct me if i'm wrong in understanding,
1.Delivery for 1st shipment,you want individual satge(from where you load the stock vide truck etc.)
2.Delivery for the 2nd shipment you wnat to reapeat the above peocess.
SriRam

Table link between shipment stage and delivery

Hi,
I am trying to find the tables which will tell me the delivery number belongs to which shipment stage.
Shipment stage I am getting from VTTS table and delivery from LIPS.
Pls. let me know. Points will be awarded.
Thanks.

VTTK-TKNUM = VTTP-TKNUM
VTTP-VBELN = LIKP-VBELN
From VTTK, VTTP you can get to know the VBELN and match it against LIKP-VBELN
Regards
Gopi

TD Shipment ouput - New filed in condition table

Hello,
We are using TD Shipment functionality. We have an output type defined under "Bulk transportation scheduling". FOr this output currently we have an access sequence which has only one table with key field as "Transportation Planning Point".
Now we need to add another table to this at higher level with key combination of "Transportation Planning Point and Issuing Plant (PSWRK). But after adding this table to the sequence we are not able to use it, as we are facing following problems:
1. Initially the field assignment was not happening so wehave defined PSWRK in the structure KOMBOI. Now the assignment is happening.
2. But when we update the shipment, the output does not get triggered. The output analysis shows that access is not made. The system is not able to fetch the value for PSWRK.
-Is it because the ouput is at header level and we have used a field that is defined at item level?
- How can we use the item level field for this output? Do we need to define it anywhere else to be picked up?
Any pointers are appreciated.
Best Regards,
Amit

Hello AMit,
If you want to use a new field for the setup of a condition table, it
has also to be defined in the structure KOMKBV7 (included in KOMB)..
In addition, you will need to make use of user exits to populate these
fields in the communication structures.
In routine LVCOMFZ1 the following User-Exits are available:
- USEREXIT_KOMPBV7_FILL (Shimpent fields for Header and Stage)
- USEREXIT_KOMPBV7_PARTNER (Shipment fields for Partner)
good luck
david

Shipment Cost- Configuration

Hii All
There is a requirement where the shipment cost should automatically pick the value of each stage in the shipment and then choose the maximum amount of the all.
Following are the questions I have :
- How can I customize shipment cost such that each stage in shipment is copied as item in shipment cost document
- How can a condition type be set so that it selects the maximum of the amount in each stage
Thanks & Regards
Gaurav Manocha

Hi,
In configiration settings of Shipment cost Calculation, you neeed to assign Shipment Pricing Procedure to both Shipment Header and Shipment Item level. I don't know the exact path but it's in Logistics Execution in SPRO. Hope this should solve your problem.
Regards
SD

Shipment cost with diff. service agent

HI,
I want to calculate shipment cost for a customer. The customer is based at location D. I am transporting materia; from locationA. From A to B my shipment type is Truck and service agent isX . From B to C my shipment type is Train and service agent is Y. From C to D my shipment type is Bus and service agent is Z.
service agent X an Y are charging on the basis of KM and Z the basis of material weigth.
I want to create and calulate a shipment document / shipment cost document one each for a service agent.Also, want to combine cost of shipment and the same should get refelect in customer invoice.
Also, let me know how should i go for automatic leg determination in shipment and about tax in shipment document?

Hi,
In bulk transportation and distribution you can assign partners at the following levels:
Shipment header
Vehicle
Shipment stage
You can assign multiple partners at each of these levels. The shipment costing process uses the partner assignments to calculate and settle costs with service providers (partners).
Activities
Partner functions and partner procedures are defined in Customizing for Sales and Distribution by choosing Basic Functions - Partner determination - Define and assign partner determination procedures. You can freely define partner functions, however, the following partner procedures must be used:
OTR
Shipment header
OTS1
Shipment stage
OTS2
Shipment transfer point
OTS3
Shipment border
OTS4
Shipment vehicle
Partner Assigned at Shipment Header Level
Partners used for the entire shipment are assigned at the Shipment Header level. You assign partners to shipments from the Shipment Header screen by choosing Goto - Partner header.
Partner Assigned at Vehicle Level
You can assign partners to vehicles within a shipment. For example, the partner could be a carrier responsible for the vehicle. A different partner can be assigned to each vehicle in the shipment. You assign partners to vehicles in the Vehicle Overview screen by choosing Goto(2) - Vehicle partner.
Alternatively, you can assign carriers to vehicles in the vehicle master data record so that the carrier is automatically proposed for the vehicle in a shipment. This partner is used for all the stages of the vehicle route, if no partner was defined in Customizing for the route or stages.
Partner Assigned at Stage Level
You can assign a different partner to each stage in a shipment. The stage type (leg, transfer point, and border crossing point) determines the partner procedure. For example, partner assignment at stage level could be used to represent a customs agent at a border crossing. You can assign partners to stages from the Document Stage Assignment screen by choosing Goto - Maintain stages - Goto(2) - Partner stages.
If you assign a partner to a route or stage in Customizing, the partner is automatically proposed for the corresponding stages of the route. If the partner is changed in the Vehicle Overview screen, then all partners which are not from Customizing are replaced with the one that was entered in the Vehicle Overview screen. You can assign partners to stages in Customizing for IS-Oil Downstream by choosing TD - TD Master Data - Route Definition - Define routes and stages.
regards,
Siddharth.

Questions Shipment cost

Dear friends
1) what is the tcode & tables to access Shipment cost Pricing Procedure?
where do we configure the same?
2) any standard functionallty is there to upload pricing conditions? for shipment cost?
Regards
Prakash

Shipment Tabels :
1)
VTFA                           Shipment Document Flow
VTTK                           Shipment Header
VTTP                           Shipment Item
VTTS                           Stage of Shipment
V_TVTF                       Shipment Cost Types
path : Logistics Execution-Transportation-Shipment Costs- Pricing-Pricing Control-Define And Assign Pricing Procedures
Table for shipment cost pricing procedure ->V_T683 Procedures (&1 &2)
2) T code TK11 to maintian condition records, you can use BDC to uploade records based on the requirement.
ALSO SEARCH IN THE FORUM WILL GET MORE DETAILS.
Regards,
Ramesh

Shipment calrification

Dear Gurus,
1) My scenario, Route doesnu2019t have stages. But when I create route with stages (from u2013to point) and tick (check) u2018shipping cost relevantu2019 in stage level of route, system is calculating the shipment cost.
Is there any way system can calculate shipment cost without check u2018shipment cost relevance indicator at stage level because I am not using stage in shipment.
2) Shipment cost type & Item category assignment
Shipment header u2013 Create shipment cost item, determines account for shipment cost item, calculate shipment cost item etc. What does this meant for pls
My scenario. 1 Delivery (has multiple line items) = 1 Shipment doc. Hence which indicator is right for me?
3) I need to penalise transporters if late delivery occurs. Can we track this through shipment? No of days to reach a destination is mentioned in route.
4) Also When I click the Shipment start date why system is not proposing shipment end date in planning tab? This will help in reporting when the shipment started, planned date to reach destination.
5) Any standard upload program available to upload route, route determination?
Please help.
Regards,
Mani

Used Multi-dimensional condition with scale.

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

Need Help in Mapping Table

Friends,
I am trying to find table where I can get Reporting Date and Reporting Time for a shipment report. Any info will be appreciated.
Thanks
Drew

Hi Andrew,
Please check table VTTS (Stage of Shipment) for city and country destination.
Also you can check table VTTK for shipment header information and table VTTP for shipment detail.
Hope this will help.
Regards,
Ferry Lianto

Let me know

What are the imp. tables frequently we use in ABAP prog. from MM and SD modules.
If possible plz give me the fields details also.

Hi
see the imp tables with fields in SD and MM modules
SALES & DISTRIBUTION MODULE RELATED TABLES:
Cycle:
EnquiryQuotationSales OrderDelivery(Picking, Packing, Post Goods
Issue and Shipment)Billing Data to FI
TABLES and Important Fields:
VBAK: Sales Document(Header Data) (VBELN)
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)
KONA: Rebate Agreements (KNUMA,VKORG,VTWEG,SPART)
VBRL: SD Document: Invoice List(VBELN,POSNR,VBELN_VF,NETWR,KUNAG)
VKDFS: SD Index: Billing Indicator(FKTYP,VBELN,FKART,VKORG)
VBSK: Collective Processing for a Sales Document Header(SAMMG,SMART)
VBSS: Collective Processing: Sales Documents(SAMMG,VBELN,SORTF)
VRKPA: Sales Index: Bills by Partner Functions(VBELN,BELNR,KUNDE,PARVW)
VRPMA: SD Index: Billing Items per Material(MATNR,VBELN,BELNR,KUNNR)
TVLKT: Delivery Type: Texts(LFART,VTEXT)
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)
MARA: Material Master-General (MATNR,MTART,MATKL)
MARC: Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD: Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
EBEW: Sales Order Stock Valuation(MATNR,VBELN,BWKEY,BWTAR)
TVKO: Sales Organizations(VKORG)
TVTW: Distribution Channel(VTWEG)
TSPA: Divisions(SPART)
TVKOV: Distribution Channels for S.Orgn(VKORG,VTWEG)
TVKOS: Divisions for S.Orgn(VKORG,SPART)
TVTA: Sales Areas(VKORG,VTWEG,SPART)
TVBUR: Sales Offices(VKBUR,ADRNR)
TVKBT: Sales Office Texts(VKBUR,SPRAS,BEZEI)
TVKBZ: Sales Office Assign.to Sales Area(VKORG,VTWEG,VKBUR)
TVKGR: Sales Group(VKGRP)
TVGRT: Sales Group Texts(VKGRP,SPRAS,BEZEI)
TVBVK: Sales Group to Sales office(VKBUR,VKGRP)
TVKWZ: Plants Assign.to S.Orgn(WERKS,VKORG)
T171T: Sales District Texts(BZIRK,BZTXT,SPRAS)
TVLA: Loading Points(LSTEL)
TVST: Shipping Points (VSTEL)
TVSWZ: Shipping Point to Plant(VSTEL,WERKS)
TVPT: Item Categories (PSTYV)
TINC: Customer Incoterms(INCO1)
T077D: Customer Account Group (KTOKD)
T001W: Plants (WERKS)
T001L: Storage Locations (LGORT)
T499S: Locations(WERKS,STAND,KTEXT)
TWLAD: To get address of Storage Location and Plant(LGORT,ADRNR)
TVAK: Sales Document (Order) Types (AUART)
TVAU: Sales Documents: Order Reasons (AUGRU)
TVFK: Billing Document Types (FKART)
TVLK: Delivery Types(LFART)
TVSB: Shipping Conditions (VSBED)
TTDS: Transportation Points(TPLST)
TVKT: Account Assignment Groups (KTGRD)
KONV: Condition Types pricing)(KNUMV,KSCHL,KWETR)
ADRC: To get Addresses of Partners(ADDRNUMBER,NAME1)
VBBE: Sales Requirements: Individual records(VBELN,POSNR,MATNR)
VBBS: Sales Requirement totals Record(MATNR,WERKS,LGORT,CHARG)
VBKA: Sales Activities Data(VBELN,KTAAR)
VBPV: Sales Document Product Proposal(VTWEG,MATNR,KUNNR,CHARG)
T682: Access Sequences (KOZGF)
T682T: Access Sequence Texts (KOZGF,VTXTM)
T683: Pricing Procedures (KALSM)
T683T: Pricing Procedures Texts(KALSM,KAPPL,SPRAS,VTEXT)
T685: Pricing Condition Types (KSCHL)
T685T: Condition Type Texts(KSCHL,SPRAS,KAPPL,VTEXT)
KONH: Conditions (Header)(KNUMH,KAPPL,KSCHL)
KONP: Conditions (Item)(KNUMH,KOPOS,KAPPL,KSCHL)
KONV: Conditions (Transaction Data)(KNUMV,KSCHL,KBERT,KWERT)
KOND: Conditions (KNUMD,ZUSKO,KSCHL)
MATERIAL MANAGEMENT MODULE:
Cycle:
Purchase RequisitionRequest for Quotation(RFQ)(Vendor Evaluation)Purchase Order(PO)Goods Receipt Note(GRN)Invoice VerificationData to FI
TABLES and Important Fields:
LFA1--Vendor Master-General (LIFNR,NAME1,ORT01)
LFB1--Vendor Master(Company Code)(LIFNR,BUKRS,PERNR)
LFC1--Vendor Master (Transaction Figures)(LIFNR,BUKRS,GJAHR)
LFM1-Pur.Orgn. Related Vendor Data (LIFNR,EKORG)
MARA--Material Master-General (MATNR,MTART,MATKL)
MARC--Material Master-Plant data(MATNR,WERKS,EKGRP)
MARD--Material Master- St.Location Data(MATNR,WERKS,LGORT,LABST)
MAKT--Material Descriptions(MATNR,MATKL,MAKTX)
MBEW--Material Valuation Data(MATNR,BWTAR)
MVKE-Material Master: Sales related Data(MATNR,VKORG,VTWEG)
MDKP--MRP related data(Header)(DTART,MATNR,PLWRK,PLSCN)
MDTB-MRP Table(DTNAM,DTPOS,PLANR)
MCHA--Batches (MATNR,WERKS,CHARG)
MCHB-Batch Stocks(MATNR,WERKS,LGORT,CHARG)
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)
ELBM-- Vendor Evaluation: Material-Related Item(LIFNR,MATNR,EKORG,INFNR,HKRIT)
ELBP- Main Criteria for Vendor Evaluation (LIFNR,EKORG,HKRIT)
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.
EQUK--Quota(header) (QUNUM,MATNR)
EQUP-Quota(item) (QUNUM,QUPOS,LIFNR)
ESLH--Service Package Header Data (PACKNO,EBELN,VBELN)
ESLL--Lines of Service Package (PACKNO)
ESUH--Ext. Services Management: Unpl.Service Limits: Header Data(PACKNO)
ESKN--Account Assignment in Service Package(PACKNO)
EKKN--Account Assignment in Purchasing Document(EBELN,EBELP,VBELN)
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)
T001W-- Plants (WERKS)
T001L-- Storage Locations (LGORT)
T300- Warehouse Numbers(LGNUM)
T301- Storage Types(LGNUM,LGTYP)
T320- Assign. Stor.Locn to WM Warehouse(WERKS,LGORT,LGNUM)
T163F--Confirmation Texts(EBTYP,EBTXT)
T156-- Movement Types(BWART)
T024-- Purchasing Groups(EKGRP,EKNAM)
T024E--Purchase Organizations(EKORG,BUKRS)
T024W--Plants Assign.to P.Orgn(WERKS,EKORG)
T161-- Purchasing Document Types(BSTYP,BSART)
T163-- Item Categorys in Purchasing Documents(PSTYP)
T149D--Valuation Types(BWTAR)
T134-- Material Types(MTART)
T179- Material Product Hierarchies(PRODH)
T179T-Material Product Hierarchies: Texts(PRODH,SPRAS,VTEXT)
TJ02T-System status texts(ISTAT,SPRAS,TXT30)
STKO-- BOM(Bill of Material)(Header)( STLTY,STLNR,STLAL)
STPO- BOM(Bill of Material)(Item)( STLTY,STLNR,STLKN,STPOZ)
STPU-- BOM Sub-Item (STLTY,STLNR,STLKN)
STPN-- BOM Follow-Up Control (STLTY,STLNR,MATNR)
STST-- Standard BOM Link (STOBJ,STLNR,STLAN,STLAL)
STZU- Permanent BOM data( STLTY,STLNR,STLAN,ALTST)
RKPF-- Document Header: Reservation(RSNUM,BWART,ANLN1,KOSTL)
RBKP-- Document Header: Invoice Receipt(BELNR,BLART,GJAHR,BUDAT)
RSEG-- Document Item: Incoming Invoice(BELNR,BUZEI,EBELN,MATNR)
Reward points for useful Answers
Regards
Anji

MultiCube Configuration

Hi All,
We have 2 ODS. We are using both to create a Multicube.
ODS1
Key
      Delivery
      Delivery Itm
      Order
      Order Itm
      Batch
Data
     Qty
ODS2
Key
     Delivery
     Delivery Itm
     Shipment Num and Stage
Data
      Shipment Num
Multicube I have identified Delivery and Delivery Itm for both ODS.
Report Requirement is
Delivery......Delivery Itm....... Order........Order ITm........Batch.........Shipment Num......... Qty
I'm able to populate everything but Shipment Num. It's coming as #.
Please suggest how I can recify the issue.
Regards,
Vivek Das Gupta

Hi,
If you are using MP you need to maintain the Charecteristics in both DSO's, here you have only Delivery & Delivery Itm are common remaing things are defets, so you can't get teh desired result in report you can see #.
You have two options.
1. Maintain all charecteristics in both DSO's using some lookups or DataSource enhancements.
2. Use InfoSet.
http://help.sap.com/saphelp_nw2004s/helpdata/en/cf/bc734190ba137de10000000a155106/content.htm
http://help.sap.com/saphelp_nw2004s/helpdata/en/ed/084e3ce0f9fe3fe10000000a114084/content.htm
Thanks
Reddy

Delveries in stages in shipment.

Similar Messages

Maybe you are looking for