Automatic determination of Delivery type and Billing type in a sales order

Hi,
I want to know that in a sales order cycle, how does automatic assignment of delivery type and billing type takes place after we create a sales order?
For example,when I create an outbound delivery for a sales order of type normal (OR) then in that case how does the system knows that it has to create an outbound delivery of type LF.How does the system propses it automatically and same is the case of billing document.

Hi
In customising the sales document type (Tcode VOV8) -
specify the default Delivery type in the field DELIVERY TYPE in the 'Shipping' area of the sales document type customisation.
Similarly you can specify the billing type in the BILLING area for both Delivery related billing and Order related billing.
Thanks,
Ravi

Similar Messages

Automatic creation of delivery ,pgi and billing as soon as ordrer is creat

Hai gurus,
Can we do automatic creation of delivery,pgi and billing as soon as order is saved.
Plz explain ?
Thanks in Advance
sameer

Hi sameer,
unless the standard program is modified you cannot do auto pgi. However batch jobs can help creating a delivery afer sales order. But incase WM is implemented then we can for the required delivery movment types create an automatic transfer order and confirmation. This brings us closer to some extent in the task. Then schedule again a job that does PGI.
can you please however explain the business need for auto pgi. It helps us to learn something as well.
regards
sadhu kishore

Auto Creation of Delivery with PGI and Billing after creation of Sale Order

Dear Experts,
I am having one Req. like...After creation of sales order ..automatic Delivery and Billing should be done.
Right now i m able to create automatic Delivery but PGI is not happening for that delivery.
Is there any configuration I have to do ... or by any user exit we can get the solution.
Can u please provide me solution for this.
Regards,
Sanket.

Hello,
yes, you can create the PGI Atomatically by BATCH JOB using the program nder the VL23 transaction code.
Goto the Transaction code SM36 to create a job for the program SAPMSSY0 which is the program for the AUTO PGI
create a variant for the Delivery document types and sales organisation combinatioans and add this variant to the bath job created in SM36.
Set the time of the Job to run after every 5 minutes, so once the job exected it will pcik all the Deliveries which are pending for the PGI.
After the PGI done you can run SDBILLDL program to create the Billing for all the document which were cleared and due for Billing.
Hope it is clear for yo, please revert if you need frther clarification .
santosh

Delivery Qty and OPEN Qty Field in SALES Order Delivery Reports.

Dear All Experts.
Please Help me for which field put for Delivery QTY. and it is necessary to calculate OPEN QTY. or we can put directly from field.
i used this field for Order Qty : WMENG.
Please Guide me.
Thnks With Regards :
Bhavesh Panchal.

Delivery qty - LIPS-LFIMG.
You cannot get open quantity directly.
use this way.
Delivery qty - LIPS-LFIMG.
order qty - VBAP-KWMENG.
open qty = delivery qty - order qty.

Header and Item Incoterms different in Sales order

Hello SAP Guru's,
I have an unique issue of Incoterms in Sales order item being different from the Header, when this happens any change to the header Incoterms is not getting copied to sales order Items.
The issue is due the different Division maintained for Sales order item in the Material master, which is fetching the Inco 2 from the Different Sales area for this is customer.
This is fine as per design where Item category is checked for Business data and Sales Document type is checked for different Division in the config.
However the Business would like the Header Incoterms to be copied to all items and any change in Header should also be copied to Line items also.
We had narrowed down on Couple of Alternatives:
Remove the Business data allowed check in the Item category config
But this would allow all Business data to be copied from sales order header to items
2. Make changes to VBKD user Exit during Sales order creation to copy the Incoterms from Sales order header to items
But this is causing multiple lines in VBKD and some issues while adding new items in VA02 ending with an Update termination.
Would like to know whether there is any other Option whether there would be least impact and also would like your advice on the better Option between the above two Options.
Thanks and Regards
Mohammed Roshan

Hi Lakshimipathi,
Finally we removed the Business Item check in the Item category which is causing the Header incoterms and any changes in Header incoterms to be copied to Sales Order line items as required but we have an issue where Sales Order item Pricing date is being greyed out due these changes, Currently the Sales order Pricing date is being determined through a Z table triggered from a User Exit which was also editable in Sales order item level.
Due to these new changes Sales order pricing date is being determined in the header and getting copied to the Sales order line item thus greying out the Sales order item pricing date field.
Would like to know your thoughts on how removing the Business Item check in Item category in VOV7 is causing the grey out of sales Order item pricing date, where the Business can modify on certain occasions and what would the workaround to restore the functionality of Sales order item pricing date.
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Message types and idoc types

hi,
     i need the list of message types and idoc types for edi.
      can any one of u pls send it.

Hi,
Check the OSS notes 104606.
The following list maps the logical messages and IDoc types to the corresponding ANSI X12 transaction sets.That is, the logical message can be copied to the transaction sets named.
204 Motor carrier shipment information
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
214 Transportation carrier shipment status message
           The logical message is TRXSTA, the IDoc type TRXSTA01. Inbound processing is supported.
304 Shipping instructions
           The logical message is SHPMNT or IFTMIN, the IDoc type SHPMNT03.
810 Invoice or billing document (also 880)
           The logical message is INVOIC, the IDoc type INVOIC01.
812 Credit and debit advice
           The logical messages are CREADV or DEBADV, the IDoc types PEXR2001 and PEXR2002.
820 Payment order and credit advice
           For the payment order, the logical message is PAYEXT (REMADV), the IDoc types PEXR2001 and PEXR2002.
           For the credit advice (ERS - Evaluated Receipt Settlement), the logical message is GSVERF, the IDoc type GSVERF01.
823 Lockbox
           The logical message is LOCKBX, the IDoc type FINSTA01. Inbound processing is supported.
830 Delivery schedule (LAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELFOR the IDOC type DELFOR01.
832 Price catalog (also 879, 888, 889)
           The logical message is PRICAT, the IDoc type PRICAT01. Outbound processing is supported.
834 Benefit enrollment and maintenance
           The logical message is BENREP, the IDoc type BENEFIT1. Outbound processing is supported.
840 Request
           The logical message is REQOTE, the IDoc types ORDERS01 to ORDERS04.
843 Quotation
           The logical message is QUOTES, the IDoc types ORDERS01 to ORDERS04.Outbound processing is supported.
850 Purchase order or order (also 875)
           The logical message is ORDERS, the IDoc types ORDERS01 to ORDERS04.
852 Stock and sale data
           The logical message is PROACT, the IDoc type PROACT01.
855 Order confirmation (also 865)
           The logical message is ORDRSP, the IDoc types ORDERS01 to ORDERS04.
856 Transport and shipping notification (ASN - Advanced Ship Notification)
           For transport in the SAP application, the logical message is SHPMNT or SHPADV, the IDoc types SHPMNT01 to SHPMNT03.
           For the delivery in the SAP application, the logic message is DESADV, the IDoc types DESADV01 (to be discontinued), DELVRY01 and DELVRY02.
860 Ordering modification (also 876)
           The logical message is ORDCHG, the IDoc types ORDERS01 to ORDERS04.
861 Credit advice (ERS - Evaluated Receipt Settlement)
           The logical message is GSVERF, the IDoc type GSVERF01.
862 Delivery schedule (FAB)
           The logic message is DELINS (from the EDI standard ODETTE) or DELJIT, the IDOC type DELFOR01.
864 Text message
           The logical message is TXTRAW, the IDoc type TXTRAW01. Inbound processing is supported.
940 Shipping order and stock order
           The logical message is SHPORD or WHSORD, the IDOC type DELVRY01.
945 Shipping confirmation and stock confirmation
           The logical message is SHPCON or WHSCON, the IDoc type DELVRY01.
997 Functional acknowledgment
           This is a technical confirmation. This is not exchanged via an individual message but the status report for IDoc processing. The status values used are:
           "22" Shipping OK, acknowledgment has yet to come
           "16" Functional acknowledgment positive
           "17" Functional acknowledgment negative
           The status values "14" and "15" are available for the Interchange Acknowledgment accordingly. Source code corrections
Cheers
VJ

Idoc type and message type

how to find the idoc type and msg type for particular delivery no.
[[i can see the idoc no in vl33n which i have to display in itab.]]

Message type. A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterizes the data sent across systems and relates to the structure of the data called an IDOC type (see below). For example, MATMAS is a message type for Material Master, and INVOIC is a message type for an Invoice (Billing Document). ALE supports over 200 message types in R/3 and about 200 application areas.

IDOC type and IDOC. An Intermediate Document (IDOC) type represents the structure of the data associated with a message type (DEBMAS02 for message type DEBMAS Customer Master, and WMMBID02 for message type WMMBXY Goods Movements), while an IDOC is an object containing the data of a particular message type. IDOCs are data containers with intelligence built in. Each IDOC contains one and only one business object. For example, an IDOC of type SHPMNT01, message type SHPMNT, will contain data only of one Shipment Document. Generally, the architecture of an IDOC is independent of the message type by virtue of ALEs ability to redefine it for any message type.
Use transaction BD64 or the following menu path to maintain the model: From the IMG (Implementation Guide), Cross-Application Components -> Distribution (ALE) (*) -> Distribution Customer Model -> Maintain Distribution Customer Model Directly -> Maintain Distribution Customer Model Directly.
Hope this helps you....
Regards,
Pavan

Difference between shipping type and shipment type

hi to all
what is teh differe nce between shiiping type and shipment type .
what is the shipment number
. can u pls tell relation between shipment and delivery tables .
sorry to ask this question ?????? pls tell the answer .

hi to all
what is teh differe nce between shiiping type and shipment type .
what is the shipment number
. can u pls tell relation between shipment and delivery tables .
sorry to ask this question ?????? pls tell the answer .

Table Types and Line Type

What is the need of Table Types,
when there is Tables.
Even when iam using in the Abap Programs in se38..
iam not getting any difference..
Even i want to about the use of Line type
when there is the structure..
iam sap 4.7 they gave that Table type describe the structure and
functional attributes of an internal table.

Way: 1:
Go to SE84 --> Select ABAP Dict --> Table Types -->
Enter the short names like ORDER wih leading and ending * on the Table Types Field. ---> F8
This will bring all related entries of Table Types(Line Types) having ORDER has a part of its Name.
Way:2:
If you know the Table Name, then go SE11 --> Putch in the Table Name --> Press Display
Now put the cursor on the Table Name field, press CNTLSHFTF3, on the WHERE USED LIST Pop up, Select only the TABLE TYPE Option and press EXECUTE.
This will bring the Table Types and Line Types.
SAP Table Types
I. Transparent tables (BKPF, VBAK, VBAP, KNA1, COEP)
Allows secondary indexes (SE11->Display Table->Indexes)
Can be buffered (SE11->Display Table->technical settings) Heavily updated tables should not be buffered.
II. Pool Tables (match codes, look up tables)
Should be accessed via primary key or
Should be buffered (SE11->Display Table->technical settings)
No secondary indexes
Select * is Ok because all columns retrieved anyway
III. Cluster Tables (BSEG,BSEC) Should be accessed via primary key - very fast retrieval otherwise very slow
No secondary indexes
Select * is Ok because all columns retrieved anyway. Performing an operation on multiple rows is more efficient than single row operations. Therefore you still want to select into an internal table. If many rows are being selected into the internal table, you might still like to retrieve specific columns to cut down on the memory required.
Statistical SQL functions (SUM, AVG, MIN, MAX, etc) not supported
Can not be buffered
IV. Buffered Tables (includes both Transparent & Pool Tables)
While buffering database tables in program memory (SELECT into internal table) is generally a good idea for performance, it is not always necessary. Some tables are already buffered in memory. These are mostly configuration tables. If a table is already buffered, then a select statement against it is very fast. To determine if a table is buffered, choose the 'technical settings' soft button from the data dictionary display of a table (SE12). Pool tables should all be buffered.
Table Types : A table type describes the structure and functional attributes of an internal table in ABAP. In ABAP programs you can reference a table type TTYP defined in the ABAP Dictionary with the command
DATA : itab TYPE TTYP.
Reafer these links below for clear ideas.
http://help.sap.com/saphelp_nw04/helpdata/en/fb/f14736a1f0ad1fe10000009b38f839/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/90/8d7304b1af11d194f600a0c929b3c3/frameset.htm
Thanks
Allot points if this helps!

Difference between fully-specified data types. and generic types

Hi,
Can anyone tell me the difference between fully-specified data types and generic types.
Thanks in advance.
Regards,
P.S.

HI
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLEincludes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
see this link
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb366d358411d1829f0000e829fbfe/content.htm
Reward if usefull

Diff b/w reference type and elementary type

hi all
can any one what is the diff b/w reference type and elementary type in data element ....
thanks
lokesh

The data type attributes of a data element can be defined by:
Specifying a domain whose attributes are copied by the data element.
Specifying a build-in type where the data type, number of places, and possibly decimal places can be directly specified.
Specifying a reference type, i.e. reference to a class, an interface, a type defined in the Dictionary, a built-in type, or a generic reference to ANY or DATA.
In the maintenance screen you can set the option you require by setting the appropriate flag (domain, built-in type, reference type) and filling in the corresponding input fields.
A reference type is a reference to another type. There are the following kinds of reference types:
Reference to a class or an interface
Reference to a type defined in the Dictionary
Generic reference to ANY, OBJECT, or DATA
Reference to a built-in Dictionary type with specification of the length and possibly also the decimal places
You can use a reference type to define the data type properties for a data element, or for typing the component of a structure or the line type of a table type.
In the field Referenced type, enter the name of a class, an interface, the generic references DATA, OBJECT, ANY, or the name of a type defined in the Dictionary. If the reference type is to be a predefined Dictionary type, choose the reference to the predefined type. Enter the number of characters and, if required, the number of decimal places.
where as
The data class describes the data format at the user interface.
If a table field or structure field or a data element is used in an ABAP program, the data class is converted to a format used by the ABAP processor. When a table is created in the database, the data class of a table field is converted to a corresponding data format of the database system used.
You can find a detailed description of the data classes allowed in the ABAP Dictionary in Overview of the Data Classes.

What is inbound XML message type and idoc type in Purchase Order response

Hi ,
We are on SRM 7 ECS , support pack SAPKIBKV08.
We have a process in which vendor will send a Purchase Order response which will be
converted to XML format by a middleware. This XML message will come to
SRM and post a POR. I want to do the EDI mapping for this XML message,
but there is no message type and idoc type in SRM for Purchase Order
response. How do I map my message type in SRM to the vendor sent fields
in middleware .
Please advise
Rgds
Sumendra

Hi,
You can process with XML without IDoc.
Vendor-> (XML) -> PI -> (XML) -> SRM.
Please check PurchaseOrderConfirmation_In in namespace "http://sap.com/xi/SRM/Procurement/Global".
http://esworkplace.sap.com
Regards,
Masa

How to trigger a form based on object type and process type

Hi all,
I am new into SRM.. I have been asked to develop a form by cloning an existing standard form..
Using bbp_output_change_sf badi you can trigger the form by passing the object type but the scenario is such that depending on the object type and process type the new form should be triggered.
The parameter iv_object_type passes the object type but how could i pass the process type ?
In the badi I noticed an import parameter is_event that has a field called transction_type that carries the process type but this field never got populated when i checked using debugger.
Please help as to how i can trigger the form based on the object_type and the process_type.
Thanx in advance.

Thanx again Jay Yang.. Well is there any possibility that you could get the items that were confirmed..
Let me eleborate..
Suppose in the PO u order an item for 10 nos and 5 gets confirmed and u return 2..
Well in my case it is that i need to fill up a field Qty returned / Qty confirmed..
I was able to get the number of items from the PO by passing the the passing the parameter to the FM "bbp_pd_conf_getdetaill"
but i dont know how to get the number of items been confirmed..
The quantity field in the line item structure gives me the number of items returned..
Can u tell me how to get the number of items been confirmed....

Calling Oracle Stored proc with record type and table Type

I have a oracle SP which takes record type and table Type which are used for order management.
Is there anay way to populate parameters with these datatypes and call the stored procedure using ODP.NET?
Please help.
Thanks in advance

Hi,
ODP supports associative arrays and REF Cursors. There is no support for PLSQL table of records.
Jenny

How does a record type and table type works

Hi,
How a record type and table type work for the ref cursor,
below i m giving an example but its giving me errors
can any one help me for this?
declare
type empcurtyp is ref cursor;
type rectype is record (veid t.emp_id%type, vename t.ename%type);
TYPE tabtype IS TABLE OF rectype;
empcv empcurtyp;
vtab tabtype;
begin
open empcv for select emp_id,ename from t;
loop
fetch empcv into vtab;
exit when empcv%notfound;
dbms_output.put_line(vtab.vename||vtab.veid);
end loop;
close empcv;
end;
here we hav table t and i m taking only two fields of the table t which r emp_id and ename.

Hi,
What errors are you getting with this? From experience you don't need a loop to put the records into the ref cursor its usually done on block.
HTHS
L :-)

Automatic determination of Delivery type and Billing type in a sales order

Similar Messages

Maybe you are looking for