Difference between rsrt and rsrt1 tcodes

Hi,
What is the difference between rsrt and rsrt1 tcode as both are used to run queries.

Hai its just about the query display difference in RSRT we can get to set list,analyzer,HTML on generalised one. where as in RSRT1 we use the views which we have created for the query already .
Also we can define different parameters in rsrt .in RSRT1 its just a single view with not much option.
other things are mostly same..
Goodday.

Similar Messages

Difference between RSRT and RSRTRACE?

Hello Guys,
Please help me to understand the use and differnec between RSRT and RSRTRACE ?
and one more Question is realted to IEMON ?
What is iemon?
what are the advantage of using iemon in BW3.5 version?
How to check whether IEMON is used in the current project or not?
If i need to download iemon - doi need to get any approval from SAP?
your answer will be highly appricated.
Thanks,
Nithi.

HI,
The Query Monitor (transaction RSRT) allows you to execute queries and to trace queries in a debug mode with several parameters (e.g., do not use aggregates, do not use buffer, show SQL statement).In the debug mode, you can investigate if the correct aggregate(s) are used and which statistics the query execution generates. For checking reasons, you can switch off the usage of aggregates, switch to no parallel processing (see for more details in the MultiProvider section) or display the SQL statement and the run schedule.
Moreover, you set some performance-related query features in RSRT: read mode and OLAP query
cache mode.
If you discover single queries that you wish to improve in terms of performance,you should execute them in RSRT in the debug mode, and analyze which aggregates are used and which statistics are generated.
The Query Trace Tool (transaction RSRTRACE) allows you to record some important function module calls and process and debug them at a later stage.
Transaction RSRCATTTRACE takes the log of RSRTRACE as input and gives aggregates suggestions for the first execution AND all further navigations performed.
Trace whole query navigations from users and analyze every step as described in the Query Monitor section.
More information can be found in BW Documentation and SAP note 99010 (Description of the trace tool for RFC links).
You can find lots more in the PDF, link given below:
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/10fb4502-111c-2a10-3080-df0e41d44bb3&overridelayout=true
Hope this helps.
Thanks,
rahul

What is the difference between rsrt and rsrq

Hi all,
Can anyone tell me the significance of these above transactions with an real time sceneario. that will be really useful. when shall we go for rsrt transaction code and when for rsrq
thanxs in advance.

hi Hari,
RSRT is used for Query monitor,
The query monitor tests, checks, and manages BI queries.
You use the query monitor to test or regenerate queries and query views, and to check or change query properties.
With the query monitor you have the option of displaying technical information about queries. Furthermore, the query monitor allows entry into the cache monitor.
The query monitor is a transaction for administrators, because previous technical knowledge is presumed
http://help.sap.com/saphelp_nw70/helpdata/en/a0/2a183d30805c59e10000000a114084/content.htm
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/2d589190-0201-0010-f19a-c74465ce6e0f
RSRQ is data load monitor,
used to check the request in monitor,
e.g we found error in ods loading, and there mentioned request number, we can then check that request with RSRQ
hope this helps.

Difference between validation and susbstittution with tcodes

hi all can any body tell me about difference between validation and susbstittution with tcodes
regars
sravya

Hi,
Settting up the FI Validations
You can use additional validation to supplement the existing SAP logic to fit you into your businness needs.
For e.g. to allow postings from company code 0001 to business area AA only.
GGB0 - To maintain the validations
Validation - Enter a validation name e.g. VBUS
Applicaion Area - SAP module e.g. FI
Calling Point - Dependent upon the application area that is selected.
0001 - Document Header - validate enteries at document header, e.g BKPF table
0002 - Line Items - check line item entris within a document, e.g. BSEG table
0003 - Complete Document - check settings for the whole documents.
e.g. Validation step 001
Allowed company code '0001' to post to business area AA only. 'FI00' checks that line item is from FI.
If checks failed, the error message number 14 is displayed to stop the transaction.
Prerequisite
<BSEG> $BUKRS = '0001' AND
<BKPF> $GLVOR = 'FI00'
Check
<BSEG> $GSBER = 'AA'
Message
Type E No. 14 - Business Area not allowed for company 0001
Output fields 1 - BSEG - GSBER 2 - BSEG - BUKRS
3 - 4
OB28 - Define Validations for Posting
CC CallPnt Validation Description Activtn Level
0001 2 VBUS Business Area Validation 1
Activtn Level - 0 - Not Active 1 - Activated 2 - Activated for all except batch input
GGB4 - Manage the activation of all validations in the SAP system.
Validations, Substitutions, and Rules
Purpose
With the validations and substitutions software, you can validate and/or substitute data at the time of entry in the FI-SL System and other SAP Systems.
Implementation Considerations
You do not need to change the standard system to customize your validations and substitutions. For each installation, you can define exactly which validations and substitutions are necessary to ensure the integrity of your data.
Features
Validation
In the SAP System, almost all input values are validated by a program or against tables or master files. Since some types of validations cannot be standardized, you can use FI-SL's validations program to create validations for your system.
With validations, you can check values and combinations of values as they are being entered in the SAP environment. Validation rules are stored in the Rule Manager; as data is entered, the Integration Manager validates the data against the validation rules stored in the Rule Manager. Because data is validated before it is posted, only valid information enters the FI-SL System.
You define validation rules using Boolean logic. When you define a validation rule, the system checks the validation rule to ensure that it is syntactically correct.
You can also define the result of breaking the validation rule. For instance, you can specify that a message is issued but the user can continue processing. You can also force the user to correct the error before processing can continue.
For more information, see Validation or What Are Validations?. For more information on using validations, see Creating a Validation. For more information on Boolean Logic, see Introduction to Boolean Logic.
Substitution
Substitution rules are stored in the Rule Manager. When data is entered in the system, it is substituted by the Integration Manager. The Integration Manager calls the Rule Manager. Substitution occurs before the data is posted to the FI-SL databases.
You define substitution rules using Boolean logic. When you define a substitution rule, the system checks the substitution rule to ensure that it is syntactically correct.
For more information, see Substitution or What Are Substitutions?. For more information on using substitutions, see Creating a Substitution. For more information on Boolean Logic, see Introduction to Boolean Logic.
Rules
A rule is a Boolean expression that you can use as a condition, as a check, or in another rule. Rules enable you to refer to frequently used Boolean statements simply by specifying the rule name.
The FI-SL Integration Manager uses Boolean logic. When you use Boolean logic and syntax, you can:
Validate data
Substitute data
Select ledgers for posting
Transfer substitution data to a rollup ledger
Select report data
The Rule Manager stores the Boolean rules used to analyze data. The Integration Manager calls the Rule Manager and determines whether entered data should be used. If a Boolean statement is true, an action is taken; if a statement is false, no action is taken.
Boolean logic is used in the following FI-SL modules:
Validation
Substitution
Ledger selection
Report Writer
Rollups
To use Boolean Logic in one of the functions listed, you create statements that are used as formulas in the FI-SL System. For more information on using Boolean Logic, see Introduction to Boolean Logic or Boolean Logic Statements and Rules.

Credit Management: Difference Between Static and Dynamic Credit Check

Hi,
Could anyone tell the difference Between Static and Dynamic Credit Check?
According to website: http://www.sap-basis-abap.com/sd/difference-between-static-and-dynamic-credit-check.htm ... this is the answer:
====================
Simple Credit Check : Tr.Code - FD32
It Considers the Doc.Value + Open Items.
Doc.Value : Sales Order Has been saved but not delivered
Open Item : Sales Order has been saved , Delivered, Billed & Transfered to FI, but not received the payment from the customer.
Static Credit Check it checks all these doc value & check with the credit limit
1) Open Doc.Value / Sales Order Value : Which is save but not delievered
2) Open Delivery Doc.Value : Which is delivered but not billed
3) Open Billing Doc.Value : Which is billed but not posted to FI
4) Open Item : Which is transfered to FI but not received from the customer.
Dynamic Credit Check         1) Open Doc
                                            2) Open Delivery
                                            3) Open Billing
                                            4) Open Items
                                            5) Horizon Period = Eg.3Months
Here the System will not consider the above 1, 2, 3 & 4 values for the lost 3 months.
====================
Question 1: Could you further explain the above information, if there is any?
Question 2:: What is the Tcode to customize settings of:
a) Simple Credit Check (isn't this same with b) below?)
b) Static Credit Check
c) Dynamic Credit Check

Hi Tanish,
Diff between Static and Dynamic Filters.
Example One at report Level.
Create a variable for a Infoobject say ,Material .
1)In the Query Designer and if u restrict it to some 10 materials at query level, the report will display for only those 10 materials only.This is Static Filter.UR AHrdcoding it to those materials.You cant change them at Query Run time.i.e not changeable by user.
2)If u give the variable as input ,and when u run the query ,u can can choose the material,may 10 may be 1 or may 20 .It is dynamic.Changeable by user at run time
Example Two at DTP and Start Routine Level,say Document Type.
1)If u give filters in Start routine it is Static as u cannot change it in Production,not changeable by user.
2)f u give filters in DTP it is Dyanamic as u can change it in Production.U can give any doc type,Changeable by user at run time.
Hope it is Understood.
Rgds
SVU

Difference between billing and invoice?

Hi all
can anybody say Difference between billing and invoice?
thanks

Hi Ipsit,
Invoice is document indicating to delivery goods and Billing is a receipt of payment
Tables are VBRK & VBRP. For flow, go to transaction VF03, enter document number and hit 'Display Document Flow' button on toolbar
VBRK and VBRP holds billing/invoice details..
Billing Document:
Generic term for invoices, credit memos, debit memos, pro forma invoices and cancellation documents.
The tables are VBRK and VBRP.
2) -- once u do PGI the delivery document will be created. There is no way to stop it.. The thing u can to do go to the list of created deliveries in VL09. Select the delivery doc which u created. There u have the option of reversing the goods or canceling it.
Billing is generic term and u can say invoice is a type of billing document.
After PGI only way left is to cancel it by Using TCODE MBST as this Tcode is used to cancel any material document.
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

Differences between LSMW and BDC

Hi All
Please can you give me the few points about the differences between LSMW and BDC?
Awaiting for your Responce
Praveen

Hai Check with the following document
GOOD
THERE IS THREE TYPE OF METHOD IN BDC
BDC SESSION
CALL TRANSACTION
CALL DIALOG
What is BDC or batch input
The Batch Input is a SAP technic that allows automating the input in transactions. It lies on a BDC (Batch Data Commands) scenario.
BDC functions:
· BDC_OPEN_GROUP : Opens a session group
· BDC_CLOSE_GROUP : Closes a session
· BDC_INSERT : Insert a BDC scenario in the session
· The ABAP statement "CALL TRANSACTION" is also called to run directly a transaction from its BDC table.
It runs the program RSBDCSUB in order to launch automatically the session. The session management is done through the transaction code SM35.
The object itself is maintanable through the transaction SE24.
BDC methods:
Method
Description
Parameters
OPEN_SESSION
Opens a session
SUBRC (Return Code 0 OK)
SESSIONNAME (Session to be created)
CLOSE_SESSION
Closes a session
None
RESET_BDCDATA
Resets the BDC Internal Table...
None. Normally, for internal purpose
BDC_DYNPRO
Handles a new screen
PROGNAME (Name of the program)
DYNPRONR (Screen Number)
BDC_FIELD
Puts a value on the screen
FIELDNAME (Name of the field)
FIELDVALUE (Value to be passed)
CONSTRUCTOR
Constructor - Initializes NO_DATA
NODATA (No data character). The constructor is called automatically when the object is created.
RUN_SESSION
Launches a session with RSBDCBTC
None
CALL_TRANSACTION
Calls a transaction with the current BDC Data
MODE (Display Mode)
UPDATE (Update Mode)
TCODE (Transaction to be called)
BDC_INSERT
Inserts the BDC scenario in the session
TCODE (Transaction to be called)
BDC techniques used in programs:
1) Building a BDC table and calling a transaction,
2) Building a session and a set of BDC scenarios and keeping the session available in SM35,
3) Building a session and lauching the transaction right after closing the session.
BDC using Call Transaction
BDC using Call transaction involves calling an SAP transaction in back ground from within the ABAP
program. The process involves building an Internal BDC table containing the screen information needed to
execute the required transaction and then passing this to the Call transaction command (See code example).
The full procedure for creating a BDC program is as follows:
What is the difference between batch input and call transaction in BDC?
Session method.
1) synchronous processing.
2) can tranfer large amount of data.
3) processing is slower.
4) error log is created
5) data is not updated until session is processed.
Call transaction.
1) asynchronous processing
2) can transfer small amount of data
3) processing is faster.
4) errors need to be handled explicitly
5) data is updated automatically
BATINPUT/DIRECT INPUT
A: Batch-inputs can not be used to fill the "delivery due list" screen because it is not a dynpro. This is a standard SAP report. A SAP report (check with "System -> Status") may be called using SUBMIT sentence with the appropriate options . It is preferred to call a report than create a Batch-input program.
GO THROUGH THIS LINK
http://www.guidancetech.com/people/holland/sap/abap/zzsni001.htm
The LSM Workbench is an SAP R/3 based tool that supports the one-time or periodic transfer of data from non-SAP systems ("legacy systems") to SAP systems.
The LSM Workbench helps you to organize your data migration project and guides you through the process by using a clear sequence of steps.
The most common conversion rules are predefined. Reusable conversion rules assure consistent data conversion for different data objects.
LSMW vs DX Workbench
The LSM Workbench covers the following steps:
Read the legacy data from one or several files (e.g. spreadsheet tables, sequential files).
Convert the data from source format to target format.
Import the data using standard interfaces (Batch Input, Direct Input, BAPI, IDoc).
Experiences made in successful implementation projects have shown that using the LSM Workbench significantly contributes to accelerating data migration.
SAP provides this tool along with documentation to customers and partners free of charge.
Users of the LSM Workbench receive the usual support via SAP Net - R/3 Frontend (component BC-SRV-DX-LSM).
Releases:
Version 1.7.2 of the LSM Workbench ("LSMW 1.7.2") available
Attention : LSMW 1.7.2 requires an SAP R/3 system with SAP R/3 4.0 or SAP R/3 4.5.
Version 1.8.0 of the LSM Workbench (1.21mb) ("LSMW 1.8.0") available
Attention : LSMW 1.8.0 requires an SAP R/3 system with SAP R/3 4.6.
Version 3.0 of the LSM Workbench (1.89mb) ("LSMW 3.0") available for Web Application Server 6.10
Attention : LSMW 3.0 requires a SAP WAS 6.10. Functionality of version 1.7.2 and 3.0 are identical !
Version 4.0 of the LSM Workbench ("LSMW 4.0") integrated in Web Application Server 6.20
Attention : LSMW 4.0 is an integrated part of SAP WAS 6.20.
Thanks & regards
Sreenivasulu P
Message was edited by: Sreenivasulu Ponnadi

Differences between BDC and LSMW

Hello SAP Gurus,
Kindly let me know the various differences between BDC and LSMW.
Also, please tell me the STEPS of the CUT-OVER PLANNING (Shifting of Data from the Legacy System to the SAP System). Here, the "Data" means which data? Please explain in details.
Looking for your early feedback.
Regards,
Kaushik.

Hi,
BDC- It is Batch data communication. Its used for data conversion from legacy system to SAP system. Only technical people can do it. Tcode is SHDB.
LSMW- It is legacy system migration workbench. Its also used for data conversion from legacy system to SAP system. But it is role of functional consultant.
There are 14 steps in LSMW. As soon as you complete the one step, automatically it will go to next step.
In general you can use LSMW. But if you want to transfer more than 40,000 data, then it is not possible in LSMW. That time you can take help of BDC.
Cutover strategy depends upon how the organizations design their data load strategies. Normally, you decide the sequence of Data loads for Configuration settings, Master data, Transaction data which follows whom and then you make a copy of the system as a Production system a day before and after checking the successful data loads, you go-live 100% or partial again depending upon organizational setup and policies.
Cutover planning is highly site specific. There's no thumb rule. The stock data as on the date of going live should be correctly entered. But stock being a highly dynamic quantity, the strategy for loading should be crystal clear. Then you have to load all the back dated transaction on the stock. Some stock comes into your plant/storage location as return and some stock is actually delivered to your customer through sales orders of various kinds.
Please refer this link,
[PP Cut over activity|http://www.sap-img.com/production/pp-questions-answers.htm]
Regards,
R.Brahmankar

Difference between me21 and me21n

hi,
plz tell me what is the difference between ME21 and ME21N transaction.....

Hi,
Me21n is a new tcode for PO with all the data gathered into a single screen ie. why called enjoy transaction ie. you can see header, item overview, item details in the single screen...
There are few new added functionalities are :
You can directly refer the other documents for making or for creation of PO via document overview
You can have exchange rates get copied..
with the enjoy transaction you can directly make PR from PO...etc..
While
me21 is old tcode for PO having all data distributed inside the main window...
Hope it helps..
Regards
Priyanka.P
AWARD IF HELPFULL
Edited by: Priyanka Paltanwale on Aug 22, 2008 7:00 AM

Difference between FD01 AND XD01 ?

HI,
Difference between FD01 AND FD02 ?

hi
good
vd01; used for sales and distribution related master records.
xd01: used for accounting related and over all master data related maintainance .
Its better u use xd01 TCODE if ur maintaning accounts related settings also.
thanks
mrutyun^

MAIN DIFFERENCES BETWEEN PARALLEL AND SEQUENTAIL PRCESSING???

HI PALS,
I WANT THE COMPLETE DIFFERENCES BETWEEN PARALLEL AND SEQUENTIAL PROCESSING!
IN THE CONTEXT OF RFC.

Hi
Parallel Processing
To achieve a balanced distribution of the system load, you can use destination additions to execute function modules in parallel tasks in any application server or in a predefined application server group of an SAP system.
Parallel-processing is implemented with a special variant of asynchonous RFC. Itu2019s important that you use only the correct variant for your own parallel processing applications: the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword. Using other variants of asynchronous RFC circumvents the built-in safeguards in the correct keyword, and can bring your system to its knees
Details are discussed in the following subsections:
·        Prerequisites for Parallel Processing
·        Function Modules and ABAP Keywords for Parallel Processing
·        Managing Resources in Parallel Processing
Prerequisites for Parallel Processing
Before you implement parallel processing, make sure that your application and your SAP system meet these requirements:
·        Logically-independent units of work:
The data processing task that is to be carried out in parallel must be logically independent of other instances of the task. That is, the task can be carried out without reference to other records from the same data set that are also being processed in parallel, and the task is not dependent upon the results of others of the parallel operations. For example, parallel processing is not suitable for data that must be sequentially processed or in which the processing of one data item is dependent upon the processing of another item of the data.
By definition, there is no guarantee that data will be processed in a particular order in parallel processing or that a particular result will be available at a given point in processing.
·        ABAP requirements:
¡        The function module that you call must be marked as externally callable. This attribute is specified in the Remote function call supported field in the function module definition (transaction SE37).
¡        The called function module may not include a function call to the destination u201CBACK.u201D
¡        The calling program should not change to a new internal session after making an asynchronous RFC call. That is, you should not use SUBMIT or CALL TRANSACTION in such a report after using CALL FUNCTION STARTING NEW TASK.
¡        You cannot use the CALL FUNCTION STARTING NEW TASK DESTINATION IN GROUP keyword to start external programs.
·        System resources:
In order to process tasks from parallel jobs, a server in your SAP system must have at least 3 dialog work processes. It must also meet the workload criteria of the parallel processing system: Dispatcher queue less than 10% full, at least one dialog work process free for processing tasks from the parallel job.
Function Modules and ABAP Keywords for Parallel Processing
You can implement parallel processing in your applications by using the following function modules and ABAP keywords:
·        SPBT_INITIALIZE: Optional function module.
Use to determine the availability of resources for parallel processing.
You can do the following:
¡        check that the parallel processing group that you have specified is correct.
¡        find out how many work processes are available so that you can more efficiently size the packets of data that are to be processed in your data.
·        CALL FUNCTION Remotefunction STARTING NEW TASK Taskname DESTINATION IN GROUP:
With this ABAP statement, you are telling the SAP system to process function module calls in parallel. Typically, youu2019ll place this keyword in a loop in which you divide up the data that is to be processed into work packets. You can pass the data that is to be processed in the form of an internal table (EXPORT, TABLE arguments). The keyword implements parallel processing by dispatching asynchronous RFC calls to the servers that are available in the RFC server group specified for the processing.
Note that your RFC calls with CALL FUNCTION are processed in work processes of type DIALOG. The DIALOG limit on processing of one dialog step (by default 300 seconds, system profile parameter rdisp/max_wprun_time) applies to these RFC calls. Keep this limit in mind when you divide up data for parallel processing calls.
·        SPBT_GET_PP_DESTINATION: Optional function module.
Call immediately after the CALL FUNCTION keyword to get the name of the server on which the parallel processing task will be run.
·        SPBT_DO_NOT_USE_SERVER: Optional function module.
Excludes a particular server from further use for processing parallel processing tasks. Use in conjunction with SPBT_GET_PP_DESTINATION if you determine that a particular server is not available for parallel processing (for example, COMMUNICATION FAILURE exception if a server becomes unavailable).
·        WAIT: ABAP keyword
WAIT UNTIL
Required if you wish to wait for all of the asynchronous parallel tasks created with CALL FUNCTION to return. This is normally a requirement for orderly background processing. May be used only if the CALL FUNCTION includes the PERFORMING ON RETURN addition.
·        RECEIVE: ABAP keyword
RECEIVE RESULTS FROM FUNCTION Remotefunction
Required if you wish to receive the results of the processing of an asynchronous RFC. RECEIVE retrieves IMPORT and TABLE parameters as well as messages and return codes.
Managing Resources in Parallel Processing
You use the following destination additions to perform parallel execution of function modules (asynchronous calls) in the SAP system:
In a predefined group of application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP Groupname
In all currently available and active application servers:
CALL FUNCTION Remotefunction STARTING NEW TASK Taskname
DESTINATION IN GROUP DEFAULT
Sequential Processing
In the following cases, the system chooses sequential (non-parallel) processing:
●      In table RSADMIN, entry QUERY_MAX_WP_DIAG has value (column value) 1.
●      The entire query consists of one sub-access only.
●      The query is running in a batch process.
●      The query was started from the query monitor (transaction RSRT) using various debug options (for example, SQL query display, execution plan display). See, Dividing a MultiProvider Query into Sub-Queries.
●      The query requests non-cumulative key figures.
●      Insufficient dialog processes are available when the query is executed. These are required for parallel processing.
●      The query is configured for non-parallel processing.
●      You want to save the result of the query in a file or a table.
In Release SAP NetWeaver 7.0, the system can efficiently manage the large intermediate results produced by parallel processing. In previous releases, the system terminated when it reached a particular intermediate result size and proceeded to read data sequentially. This is no longer the case. Therefore, the RSADMIN parameter that was used in previous releases for reading a MultiProvider sequentially is no longer used.
Reward If Helpfull,
Naresh

Difference between ME_READ_PO_FOR_PRINTING and ME_PRINT_PO

I just saw these 2 function modules in standard PO printing program SAPFM06P. Can someone please let me know whatz the difference between ME_READ_PO_FOR_PRINTING and ME_PRINT_PO function modules...

Hi friend......
The function module ME_READ_PO_FOR_PRINTING is used to read the PO
The function module ME_PRINT_PO is used to print the PO
if u want let u know some more information
How can i get PO partner functions using FM ME_READ_PO_FOR_PRINTING
http://sap.ittoolbox.com/groups/technical-functional/sap-log-mm/tcode-me9f-user-exit-exit_saplmedruck_001-617362

Difference between Park and Hold PO invoices

Hi,
Anybody knows the difference between parking and holding a PO invoice? The tcodes are MIR7 and MIRO respectively.
Regards.

hi,
In Park document, enter the invoice data. It does not matter if:
- Your entries are complete or incomplete
- The balance of the document is zero or not
The system does not carry out any checks, as you can correct or add more information to a parked document later on.
In two scenario, Invoice document will be parked.
1. An employee is interrupted or clarify certain issues when entering an invoice. He or she can park the document and continue processing it later on with save at that stage without entering data twice.
2. Organizational process is in such a way that one employee parks invoices without checking them. Another employee then performs invoice verification and posts the parked documents, possibly after changing them

Report - quantity and value difference between delivery and invoice?

Hello experts,
My client use u201EProof of deliveryu201D t-code: VLPOD. There is always quantity and value difference between delivery and invoice.
Do you know any report which will show this differences between delivery and invoice?
Best regards,
Maciej

Hi,
Note 867678 - Proof of delivery (POD), delivery and billing document will help you to understand POD flow.
You have the tcode VLPODF/VLPODL/VLPODA, but perhaps they will not help you. So, as the before note suggests you, you can use the tables VBFA, LIKP, LIPS, VBRK, VBRP, TVPOD and TVPODG to do your own report.
I hope this helps you
Regard,
Eduardo

Difference between VL10 and JITK

Hello,
How to explain to a user difference between VL10 and JITK ?
Thanks.
Romeo

Dear Romeo,
As my friend said n even u'll b aware of: VL10 is a T-code using which u can create a delivery in foreground giving the details like sales order, shipping point & delivery date as the selection. Thus it's used 4 normal del creation.
Whereas JITK is a TCode for "Summarized JIT Calls Due for Delivery" which is one fo the SAP best prcatices for Automotive only. The other point of diff is that u can create deliveries in the background only using JITK. It is not possible to process summarized JIT calls online. JIT calls as u know r there in the shcelduing agreement along with the forecast tab thus giving the xact 1,2 weeks requirement from d customer.
Hope it'll b enuf 2 convince d user.
regards
PARAM

Difference between rsrt and rsrt1 tcodes

Similar Messages

Maybe you are looking for