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 .

Similar Messages

What is the difference between partner function and partner type

Hi Gurus,
What is the difference between partner function and partner type?
Thanks,
Paul

Hi John,
The partner types allow us to distinguish between different business partners such as customer, vendor, employee etc and the partner functions represent the functionality or role each partner plays within the business transaction.
For example under the partner type Customer, you will find - Sold to party, Ship to party, Bill to party, Payer.
The business partners that exist in the market place are represented with a partner type in the R/3 system. Examples of business partners are customer, vendor, employee and contact person.
The following partner types are defined in the partner processing for the sales & distribution module
a.     AP contact person (06)
b.     KU customer (07)
c.     LI vendor (08)
d.     PE employee/personnel (09)
Assigning the partner functions in the SAP system determines the functions of particular partner in the sales process. One partner may take on several functions also.
REWARD POINTS IF HELPFUL
Regards
Sai

Difference between shipping invoice and fiscal invoice?

Helo.
Can anyone tell me the difference between Shipping Invoice and Fiscal Invoice?
Regards
Points are assured

Hi Kulkarni,
Invoice Processing
Process
You can use this business process to display and process invoices both in SAP Enterprise Buyer (SAP EBP) and SAP Supplier Self-Services (SAP SUS).
As supplier or service provider, all invoices that you enter or process in SAP Enterprise Buyer must be approved by a responsible internal employee. For goods and services with a low purchase value, invoices and credit memos can also be created without a purchase order reference. Moreover, it is also possible to create express invoices in the check status application.
In SAP Supplier Self-Services (SAP SUS) invoices can be entered with reference to a purchase order, shipping notification, or contact person before they are sent to the customer.
If, following a purchase order, the goods supplied or the service provided turn out to be defective or the price charged is too high, you as an internal employee, supplier, or service provider, can enter and process credit memos or subsequent debits/credits in SAP Enterprise Buyer
i think the invoice generated during a particular fiscal year is fiscal invoice.
thanks
sekjar

Difference between Shipping function and install function in O2A

Hi,
I am asking this query from domain perspective than from technology. There are two functions in O2A namely install order and shipping function. Can anyone please explain the activities under these function.
1. Engineer takes the equipment to customer premises: Is this install order of ship function?
2. Is shipping function related to supply chain from vendor perspective and not customer perspective.
Please let me know your views. Thanks

According to me the logic might be Shipping and Install functions are mutually exclusive. So The scenario might be like this:-
Shipping Function:-
1. Some shipping company ships the equipment to the customer and that is tracked in CSP's system that customer has received the shipment.
Install function:-
2. Customer would have confirmed some appointment date in CAF form.
3. Field Engineer will then goto the customer premises and then install the equipment.

Difference between Return Po and Retuning with 122 movement type

Dear Experts,
i need some clarification on Return Po and retuning goods with 122 movement type in the context of Excise invoice.
in our previous company we used 122 movement we capture excise invoice with J1IS and referring the incoming excise
and return the material to vendor.
in present company we are directly doing return Po and capturing excise invoice with J1is,here we are not capturing against the
incoming excise,please clarify me.
Regards,
Varun

Hi,
Refer the below thread:
Difference between 102, 122 and 161
In terms of stock movement, both 122 and 161 represents the return delivery to your vendor. The difference takes place in terms of how you are returning your delivery to your vendor - It is movement type 161 that SAP will automatically propose if your return PO is referenced. Otherwise, 122 movement type will be used instead.
Regards,
Prashant
Edited by: Prashant Prasad on Apr 22, 2011 8:51 AM

The difference between FIELD-SYMBOL and normal DATA TYPE

Dear experts,
Please see the example below, both are output the same result.
DATA: EXTERNAL_RECORD(4000),
      POSITION TYPE I,
      LENGTH TYPE N,
      ENTRY TYPE STRING.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
    EXIT.
ENDIF.
ADD 4 TO POSITION.
MOVE EXTERNAL_RECORD+POSITION(LENGTH) TO ENTRY.
WRITE ENTRY.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
    EXIT.
ENDIF.
ENDDO.
--OR It can be written as--
DATA: EXTERNAL_RECORD(4000),
      POSITION TYPE I,
      LENGTH TYPE N.
FIELD-SYMBOLS <ENTRY>.
EXTERNAL_RECORD = '0005Smith0007Edwards0005Young'.
DO.
LENGTH = EXTERNAL_RECORD+POSITION(4).
IF LENGTH = 0.
    EXIT.
ENDIF.
ADD 4 TO POSITION.
ASSIGN EXTERNAL_RECORD+POSITION(LENGTH) TO <ENTRY>.
WRITE <ENTRY>.
ADD LENGTH TO POSITION.
IF POSITION >= 4000.
    EXIT.
ENDIF.
ENDDO.
Is there any special circumstances we need to use FIELD-SYMBOL?
Why is FIELD-SYMBOL is introduce in the first place?
Kindly advice with example.
Thanks in advance for those who can help me on this.

HI,
You can use field symbols to make the program more dynamic. In this example the name of a table control is substituted by a field symbol. Thus you cal call the form with any internal table, using the name of the table control as a parameter.
Example
form insert_row
using p_tc_name.
field-symbols <tc> type cxtab_control. "Table control
assign (p_tc_name) to <tc>.
insert 100 lines in table control
<tc>-lines = 100.
Field symbols allow you to:
**     Assign an alias to a data object(for example, a shortened
        name for data objects structured through several hierarchies
        - <fs>-f instead of rec1-rec2-rec3-f)
**     Set the offset and length for a string variably at runtime
**     Set a pointer to a data object that you determine at runtime (dynamic ASSIGN)
**     Adopt or change the type of a field dynamically at runtime
**     Access components of a structure
**     (from Release 4.5A) Point to lines of an internal table
        (process internal tables without a separate work area)
Field symbols in ABAP are similar to pointers in other programming
languages. However, pointers (as used in PASCAL or C) differ from ABAP
field symbols in their reference syntax.
The statement ASSIGN f to <fs> assigns the field f to field
symbol <fs>. The field symbol <fs> then "points" to the
contents of field f at runtime. This means that all changes to the
contents of f are visible in <fs> and vice versa. You declare
the field symbol <fs> using the statement FIELD-SYMBOLS: <fs>.
Reference syntax
Programming languages such as PASCAL and C use a dereferencing symbol
to indicate the difference between a reference and the object to which
it refers; so PASCAL would use p^ for a pointer instead of p, C would
use *p instead of p. ABAP does not have any such dereferencing symbol.
**     In PASCAL or C, if you assign a pointer p1 to a pointer p2,
you force p1 to point to the object to which p2 refers (reference semantics).
**     In ABAP, if you assign a field symbol <fs1> to a field
symbol <fs2>, <fs1> takes the value of the data object to
which <fs2> refers (value semantics).
**     Field symbols in ABAP are always dereferenced, that is,
they always access the referenced data object. If you want to
change the reference yourself in ABAP, you can use the ASSIGN statement
to assign field symbol <fs1> to field symbol <fs2>.
Using field symbols
You declare field symbols using the FIELD-SYMBOLS statement.
They may be declared either with or without a specific type.
At runtime you assign a field to the field symbol using the ASSIGN
statement. All of the operations on the field symbol act on the field
assigned to it.
When you assign a field to an untyped field symbol, the field symbol
adopts the type of the field. If, on the other hand, you want to assign
a field to a typed field symbol, the type of the field and that of the
field symbol must be compatible.
A field symbol can point to any data object and from Release 4.5A,
they can also point to lines of internal tables.
The brackets (<>) are part of the syntax.
Use the expression <fs> IS ASSIGNED to find out whether the field
symbol <fs> is assigned to a field.
The statement UNASSIGN <fs> sets the field symbol <fs> so
that it points to nothing. The logical expression <fs>
IS ASSIGNED is then false. The corresponding negative expression
is IF NOT <fs> IS ASSIGNED.
An unassigned field symbol <fs> behaves as a constant with
type C(1) and initial value SPACE.
MOVE <fs>
TO dest     Transfers the initial value SPACE to the variable dest
MOVE 'A' to <fs>
Not possible, since <fs> is a constant
(runtime error).
To lift a type restriction, use the CASTING addition in the
ASSIGN statement. The data object is then interpreted as though
it had the data type of the field symbol. You can also do this
with untyped field symbols using the CASTING TYPE <type> addition.
The danger with pointers is that they may point to invalid areas.
This danger is not so acute in ABAP, because the language does not
use address arithmetic (for example, in other languages, pointer p
might point to address 1024. After the statement p = p + 10, it would
point to the address 1034). However, the danger does still exist, and
memory protection violations lead to runtime errors.
A pointer in ABAP may not point beyond a segment boundary. ABAP does
not have one large address space, but rather a set of segments.
Each of the following has its own segment:
*     All global data
*     All local data
*     Each table work area (TABLES)
*     Each COMMON PART
You should only let field symbols move within an elementary field or
structure where ABAP allows you to assign both within the global data
and beyond a field boundary.
Rgds
Umakanth

What's the difference between segment filtering and reduced message type

Hi gurus,
What's the difference between segment filtering and reduced message type? It seems they have the same functionality: Reduce the segment while idoc is generated.
Thanks in advance.

Hi,
BD53 is for IDoc Reduction.
this allows you to create a reduced message based upon a standard message type.If you want see mandatory fields. go to T-coe BD53 and give one standard messege type name and eg: matmas
there mandatory fields will be in Green color..
And BD56- This transaction is used to filter out segments of IDocs for combination of sender and receiver. This is usefull in scenarios where a standard IDoc with many segments is used but the receiving partner is only interested in some of the segments
the table related to this transation is TBD20
please go through below blog you have an idea abt that,
http://wiki.sdn.sap.com/wiki/display/ABAP/ReducedMessageTypes
http://saptotal.com/IDoc%20Segment%20Filtering.html
regards,
ganesh.

Difference between message type and idoc type

Hi
difference between message type and idoc type
Regards
Rama

Hi,
Message Type:
A message type represents the application message exchanged between R/3 systems and R/3 and an external system. A message type characterises the data sent across systems and relates to the structure of the data called an IDOC type.
Diff. with IDOC type
An IDoc type specifies the structure of the data.
A message type specifies the meaning of the data
Diff. b/w IDOC type and IDOC
An IDoc type is the definition of a specific data structure.
An IDoc is an actual instance of data based on an IDoc type. Therefore, there can be many IDocs created from a single IDoc type.
Example:
MATMAS is the message type and MATMAS05 is IDoc type for Material Master.
Thanks,
Shankar

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
<b>Reward if usefull</b>

Difference between line type and table type

hi,
can any one explain the difference between line type and table type . and how to declare a internal table and work area in BSP's

hi,
Go through this blog, this might help you.
/people/tomas.altman/blog/2004/12/13/sdn-blog-how-to-do-internal-tables-in-bsp
People who have worked with ABAP for a while sometimes forget that the internal table concept is rather different than what exists in most programming languages. It is very powerful, but at the same time can be confusing.
In SAP it is possible to have a table which is the rows and a headerline which is the working area or structure which can then be commited to the table.
With a BSP, if we try to create an internal table within the BSP event or layout we will get the following error: mso-bidi-
                        "InternalTableX" is not an internal table - the "OCCURS n" specification is mso-bidi- missing.
class="MsoNormal"><![if !supportEmptyParas]>The problem we are seeing as an inconsistency has to do with the difference between classic ABAP and ABAP Objects. When SAP introduced ABAP Objects they decided to clean up some of the legacy syntax and create stricter rules. However they didn't want to break the millions of line of code that already existed, so they only implemented these stricter checks when OO is being used. Therefore you can declare a table with a header line in a regular ABAP program or Function Module but you can't have one with a header line in OO.
Because everything in BSP generates ABAP OO classes behind the scenes, you get these same stricter syntax checks. My suggestion is that you have a look in the on-line help at the section on ABAP Objects and always follow the newer syntax rules even when writing classic ABAP programs.
In a BSP when we need to work with a table we must always do the following:
1, in the Types definitions create a structure:
                        types : begin of ts_reclist,
mso-bidi-        style='mso-tab-count:2'>                            receiver type somlreci1-receiver,
mso-bidi-        style='mso-tab-count:2'>                 style='mso-tab-count: 1'>             rec_type type somlreci1-rec_type,
mso-bidi-         style='mso-tab-count:2'>                            end of ts_reclist.
mso-bidi- <![if !supportEmptyParas]> <![endif]>
but we must remember this is only a structure definition and we cannot store anything in it, although we can use it elsewhere as a definition for Structures(WorkAreas)
2, in our Types definitions (this is the best place for this one as we can then access it from many areas without having to create it locally) so in the Types definitions we must create a TableType:
class="MsoNormal">                         types : tt_reclist type table of ts_reclist.
class="MsoNormal"><![if !supportEmptyParas]> <![endif]> this TableType is our table definition and again we cannot store anything in it, but we can use it elsewhere as a definition for InternalTables
3, now that you have laid the foundations you can build and in the event handler, it is now simply a case of creating the InternalTable based upon the Table definition:
                       data: t_reclist type tt_reclist.
and creating the structure based upon the structure definiton:
<![if !supportEmptyParas]>   <![endif]>                         data: s_reclist type ts_reclist.
as described above, the structure becomes the work area and this is where you assign new values for elements of the table eg:<![endif]>
                        s_reclist-receiver = '[email protected]'.   "<-- change address
mso-bidi- <![if !supportEmptyParas]> <![endif]>
mso-bidi-                         s_reclist-rec_type = 'U'.
and then once the data is in the elements of the structure, the structure can be appended to the internal table as follows: class="MsoNormal">
                        append s_reclist to t_reclist.
<![if !supportEmptyParas]> <![endif]>
the internal table will then be readable for the ABAP function and can be applied for example as follows: class="style1">           style='mso-tab-count:1; font-family: "Courier New", Courier, mono;'>
class="style1">CALL FUNCTION 'SO_NEW_DOCUMENT_SEND_API1'
                        EXPORTING
style='mso-tab-count:2'>                                    document_data = docdata
style='mso-tab-count:2'>                                    DOCUMENT_TYPE = 'RAW'
style='mso-tab-count:2'>                                    PUT_IN_OUTBOX = 'X'
style='mso-tab-count:2'>                                    COMMIT_WORK = 'X' "used from rel.6.10
                        TABLES
mso-bidi-font-size: style='mso-tab-count:2'>                                    receivers = t_reclist
class="style1"> <![if !supportEmptyParas]>   <![endif]>
<![if !supportEmptyParas]>F inally, a comment from Thomas Jung,
<![if !supportEmptyParas]> when defining my work area for an internal table I like to use the like line of statement. That way if I change the structure of my table type, I know that my work area will still be OK. Second, your types and table types don't have to just be declared in your code. You can create a table type in the data dictionary and use it across multiple programs(also great for method and function parameters). I really push hard for the other developers at my company to use the Data Dictionary Types more and more.
Hope this helps, Do reward.

Difference Between Data type and message type

Hi,
    i have doubt on data type and message type.why we are mapping the message type why not data type?wht is the difference between data type and message type?

Hi Narayanana,
Data type defines the structure of your xml message.Message type is the wrapper of data type.You will be using your message type while mapping and not the data type.Its the abstraction concept used in oops
kanan thiyam
Posts: 28
Questions: 7
Registered: 1/8/07
Forum points: 24
   Re: What is deffernce b/w Data type and message type
Posted: Jun 13, 2007 8:05 AM    in response to: suresh k         Reply      E-mail this post
Hi Suresh,
Data Type defines the structure of the message and it will be wrapped under Message Type.
Hope the details below will clearify your doubts.
A data type in a programming language is a set of data with values having predefined characteristics. Examples of data types are: integer, floating point unit number, character, string, and pointer.
The characteristic of columns and variables that defines what types of data values they can store.
Check out the details:
http://en.wikipedia.org/wiki/Data_type
A message type comprises a data type that describes the structure of a message. At the following points in SAP Exchange Infrastructure you can refer to the message to be exchanged at runtime by using the message type:
Details:
http://help.sap.com/saphelp_nw04/helpdata/en/2d/c0633c3a892251e10000000a114084/content.htm
kanan

Difference between IDOC Type and Message Type

Hi, please let me know the difference between IDOC type and Message Type?
Thanks

Hi,
Message type is business name for IDOC you are sending hiding all technical details of the IDOC.
IDOC type gives more technical information about structure of the IDOC.
You will be linking IDOC type to message type while processing IDOC in runtime. You will be specifying message type and IDOC type in WE20 trasaction which says which message will go to which partner whether it is outbound or inbound.
Best Regards,
Krishna

[svn] 4112: Further work for FXG to SWF transcoding - checking in some work resulting from collaborating with Kaushal to correct FXG transforms and gradient transforms as well as cater for differences between Java AffineTransform and the SWF Matrix type .

Revision: 4112
Author: [email protected]
Date: 2008-11-14 10:05:42 -0800 (Fri, 14 Nov 2008)
Log Message:
Further work for FXG to SWF transcoding - checking in some work resulting from collaborating with Kaushal to correct FXG transforms and gradient transforms as well as cater for differences between Java AffineTransform and the SWF Matrix type.
QE: Not yet.
Doc: No
Checkintests: Pass
Reviewer: Kaushal
Modified Paths:
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/GraphicContentNode.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/fills/LinearGradientFillNode.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/fills/RadialGradientFillNode.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/strokes/LinearGradientStrokeNode.j ava
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/strokes/RadialGradientStrokeNode.j ava
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/swf/AbstractFXGGraphics.java
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/swf/TypeHelper.java
Added Paths:
flex/sdk/trunk/modules/swfutils/src/java/flash/fxg/dom/ScalableGradientNode.java

Difference between Storage Unit type and storage type

Hi,
I am confused with storage unit type and storage type.
Can anyone help me with real case examples.
I would like to know about Storage unit types and their uses in WM.

Hello!
Storage type is a storage area and Storage Unit Type is strategies are used in the warehouse process for creating transfer orders.
A storage type is a storage area, warehouse facility, or a warehouse zone that you define in Warehouse Management (WM) for a warehouse number. This is a physical or logical subdivision of a warehouse complex that is characterized by its warehouse technique, the space used, its organizational form, or its function. A storage type generally contains several storage spaces or slots. These are called storage bins in Warehouse Management (WM).
See also:
https://wiki.sdn.sap.com/wiki/display/ERPSCM/WMOrganisationalStructure
http://help.sap.com/saphelp_470/helpdata/en/c6/f838f94afa11d182b90000e829fbfe/content.htm
Storage Unit Type is putaway strategy, the system processes different storage unit types (for example, pallets) and allocates them to the appropriate section. Often, one storage bin is divided into several smaller sections. Typically, only the same storage unit types can be placed into a storage bin at one time.
See also:
http://wiki.sdn.sap.com/wiki/display/ERPSCM/PutawayandRemovalStrategiesin+WM
http://help.sap.com/saphelp_470/helpdata/en/c6/f844c44afa11d182b90000e829fbfe/content.htm
Milca

Difference between DEclaring Itab with DATA & TYpe Statement?

HI Friends,
What is the Difference between Declaring Itab with DATA & TYpe Statement?

Hi,
The Statements TYPES and DATA
Each ABAP program define its own data types using the statement.
TYPES dtype TYPE type ...
and declare its own variables or instance attributes of classes using the statement
DATA var {TYPE type} ...
Within the program or a class, you can also define local data types and variables within procedures. Local variables in procedures obscure identically-named variables in the main program or class.
When creating data types and data objects, there are a number of naming convention that also apply for other local program definitions, such as procedures. These are described in detail in the keyword documentation.
The Additions TYPE and LIKE
The additions TYPE type and LIKE dobj are used in various ABAP statements. The additions can have various meanings, depending on the syntax and context.
·        Definition of local types in a program
·        Declaration of data objects
·        Dynamic creation of data objects
·        Specification of the type of formal parameters in subroutines
·        Specification of the type of formal parameters in methods
·        Specification of the type of field symbols
TYPES: BEGIN OF struct,
         number_1 TYPE i,
         number_2 TYPE p DECIMALS 2,
       END OF struct.
DATA: wa_struct TYPE struct,
       number    LIKE wa_struct-number_2,
       date      LIKE sy-datum,
       time      TYPE t,
       text      TYPE string,
       company   TYPE s_carr_id.
This example declares variables with reference to the internal type STRUCT in the program, a component of an existing data object wa_struct, the predefined data object SY-DATUM, the predefined ABAP type t and STRING, and the data element S_CARR_ID from the ABAP Dictionary.
Reward Points if found helpfull..
Cheers,
Chandra Sekhar.

Difference between shipping type and shipment type

Similar Messages

Maybe you are looking for