Difference between COPC planning and cost object controlling

I want to know why do we have to calculate the cost of a manufactured product by both COPC planning and Cost object controlling by order?
Will the cost of a manufactured product be different in COPC planning method and cost object controlling method?
if we use only cost object controlling to calculaute the cost of a manufactured product without using COPC planning wht will be the implications?

Raja,
Yes the cost can be different. The cost calculating thorught Product Cost Planning may be static, you calculate it by period it is more for planning prupose ans to set standard. The cost calculated through Cost Object Controlling is resulting from your actual transactions, and the are few variables that could increase or decrease the cost of product. For example the overhead cost (Increase of salaries) can directly affect your activity rate at the work center and impact cost of your product when the production order is complete. You need both costs (Cost Planning and Cost Object releated) so at the end of the period you can calculate variance betweeen your plan cost and your actual costs.
Hope this clarifies your doubts.
GG

Similar Messages

What is major difference between hyperion planning and hyperion essbase

hi
what is the differences between hyperion planning and hyperion essbase.i dont know about planning much.but as far i know.i think we can do every thing in essbase also(planning,budgeting and forecasting)
what u say.what we actually do in planning.
regards
bharat

Hi Bharat
Although as you mention in your post Essbase can do plans/budgets etc it may not be simple to provide complex planning process control and ease of data entry etc.
Planning delivers these benefits and some through web delivered components such as forms, business rules and workflow for instance. There are some restrictions to using planning and these need tobe well understood before embarking on a project.
It would be worth having a look at product sheets from Oracle and/or presentations from various events to get a feel for planning capabilities.
Hope this helps.
Andy King
http://www.analitica.co.uk

What is the basic difference between Hyperion Planning and HFM

Hi GURU'S,
what is the basic difference between Hyperion Planning and HFM and when do we choose them.

On a high level the difference is this:
1. HFM is best for global collection (collecting data from scattered entities), group consolidation and for easily structuring financial reporting (mainly consisting of financial data)
2. Planning is best for modeling your business, starting from a demand forecast and arriving to capacity planning and finally to financial statements, by utilizing business drivers (non-financial data like volumes, prices, productivity rates etc)
Of course, differences may be analyzed at several levels down to technical, but the discussion may turn out to be too long, yet adding little value to the question: "when do we choose the one over the other". Bear in mind that your requirements may turn out that you need both.

Difference between Classic Planning and EPMA Application

Hi All,
We are currently working Hyperion Planning version 9.3.1 and we do use Classic Planning Administration. We are in the phase of upgrading to version 11.1.2 and thinking of using Enterprise Performance Management Architecture to work with applications . Kindly let me the difference between Classic Planning and EPMA Application and its cosequences on upgradation.
Thanks in advance

Instead of explaining it all again here are some posts around the same subject
Re: what is the Differenc between Classic Planning and EPMA
Hyperion Planning - Classic Administration vs EPMA ....
Re: The advantage of using EPMA?
EPMA compare to Classic
Cheers
John
http://john-goodwin.blogspot.com/

Difference between value category and cost element

Hi I am new to SAP Pm.can anyone explain me the difference between value category and cost element and how are they linked with examples

HI Pallavi,
Value Category are use to devide your total cost in to diffrent elements for example Material, External Services, Internal Services etc. If you dont have any value category configured then all cost will show together.
Cost Element are the cost collector where your cost will be booked means different cost under different Elements.
So What you need to do You need to create one Value category Like material or any thing then you need to assign all Cost Elements which will be used to book cost related to Material or that perticular category. You can assign Cost Element directly, range or as a group to these category under SPRO.
Regards,
SS

Differences between DATA TYPE and DATA OBJECTS

I am new to ABAP,I want to know the differences between DATA TYPE and DATA OBJECTS with some examples.
please help me regarding this.

Hi Ashish,
Data Types:       Are pure descriptions.
               No memory is associated with data types.
               Describes the technical properties of data objects.
EX.
1.     C-CHARACTER
2.     D-DATE
3.     F-FLOAT
4.     I-INTEGER
5.     N-NUMERIC TEXT
6.     T-TIME
7.     P-PACKED NUMBER
8.     X-HEXADECIMAL
9.     STRING-Variable length string.
10.     XSTRING-Variable length byte string.
Data Objects: Are created during runtime.
                They cannot exist without the data Types.
                Occupies memory space.
EX:
1.     INTERNAL DATA OBJECT- Internal Data objects
     LITEERAL- A literal has a fixed value.Ex: WRITE:u201DWORK HARDu201D.
     VARIABLES: Data statement is used to create variables.
EX.DATA: NUM TYPE I.
NUM: VARIABLE defined by data statement.
EX: DATA: PRICE LIKE NUM.
     CONSTANT-It is a data object, which contains a constant value throughout the program.
Can be declared in program by using CONSTANT statement.
EX:CONSTANT: INT TYPE I VALUE 15.
2.     EXTERNAL DATA OBJECT: Are defined in tables i.e In ABAP/4 dictionary you can access this data from table.
         EX: TABLES: SFLIGHT
          DATA: SEATS LIKE SFLIGHT-SEATSMAX.
3.     SYSTEM DEFINED DATA OBJECTS:Space & system variables like SY-UNAME,SY-DATUM, SY-REPID.
4.     SPECIAL DATA OBJECTS:
     PARAMETERS: Are Variables ,which can accept value from user.
      SELECTION SCREEN : Are special internal tables to accept value ranges from user.
3 APPROACHES TO DEFINE DATA OBJECTS.
1.     ELEMENTARY TYPES
DATA: Customer _Name (25) TYPE C,
               Vendor_Name (25) TYPE C.
2.     REFRENCE TO AN EXISTING FIELD:
DATA: Customer _Name2 (25) TYPE C,
              Vendor_Name2 (25) LIKE Customer_Name2
3.     REFRENCE TO NON-ELEMENTARY TYPE:
TYPES: T_NAME (25) TYPE C
DATA: CUSTOMER_NAME TYPE T_NAME
               VENDOR_NAME TYPE T_NAME
4.     RECORD-Information in rows & columns.
DATA: BEGIN OF BOOKING,
                                ID (4) TYPE C,
                                FLIGHT_DATE TYPE D,
                                NAME LIKE CUSTOMER_NAME,
                                END OF BOOKING.
You can also look into SAP help for more information.
Regards,
Indu.

Difference Between Data Type and Data Object

Difference Between Data Type and Data Object

hi magesh
Data types can be divided into
elementary,
reference, and
complex types.
Elementary Types
Elementary types are the smallest indivisible unit of types. They can be grouped as those with fixed length and those with variable length.
Fixed-Length Elementary Types
There are eight predefined types in ABAP with fixed length:
Four character types:
Character (C),
Numeric character (N),
Date (D),
and Time (T).
One hexadecimal type:
Byte field (X).
Three numeric types:
Integer (I),
Floating-point number (F)
and Packed number (P).
Variable-Length Elementary Types
There are two predefined types in ABAP with variable length:
STRING for character strings
XSTRING for byte strings
Reference Types
Reference types
describe data objects that contain references (pointers) to other objects (data objects and objects in ABAP Objects).
Data Types
1) As well as occurring as attributes of a data object, data types can also be defined independently.
2)You can then use them later on in conjunction with a data object.
3) The definition of a user-defined data type is based on a set of predefined elementary data types.
4) You can define data types either locally in the declaration part of a program using the TYPESstatement) or globally in the ABAP Dictionary.
5) You can use your own data types to declare data objects or to check the types of parameters in generic operations.
Data Objects
1)Data objects are the physical units with which ABAP statements work at runtime.
2) The contents of a data object occupy memory space in the program.
3) ABAP statements access these contents by addressing the name of the data object and interpret them according to the data type..
4) For example, statements can write the contents of data objects in lists or in the database, they can pass them to and receive them from routines, they can change them by assigning new values, and they can compare them in logical expressions.
5) Each ABAP data object has a set of technical attributes, which are fully defined at all times when an ABAP program is running (field length, number of decimal places, and data type).
6) You declare data objects either statically in the declaration part of an ABAP program (the most important statement for this is DATA), or dynamically at runtime (for example, when you call procedures).
7) As well as fields in the memory area of the program, the program also treats literals like data objects.
hope this helps u,
reward points if useful
Ginni

Difference between Pension plans and savings plans

Dear Friends,
I'm familiar with the configuration of savings plans. But I have no idea about the pension plans. I realize that some of the basic steps are common to both savings and pension plans but what is the main difference from a config perspective?.
If any one can kindly explain the necessary steps to set up pension plans or if there is any document which talks about it please please let me know.
I appreciate the help and thanks in advance.

IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Minimum and Maximum Number of Dependents
Define Cost Variants:
In this step you define cost variants to determine which factors influence the cost of a health plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Option
u2022 Dependent coverage
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often costs vary for all the combinations of option and dependent coverage that you have defined in each plan.
This indicates how many cost variants you need. You can use the same cost variant more than once, for example, if costs are always identical for the dependent coverages 'employee only' and 'employee plus family' within a plan, regardless of the plan option
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Define Cost Rule
Health Plan Attributes:
In this step, you bring together all the definitions relevant to the health plan that you have made in the previous steps.
You assign to each health plan:
u2022 Its options
u2022 Relevant dependent coverages
u2022 The cost variants for the combination of options and dependent coverages
IMG Path: Personnel Management  Benefits  Plans  Health Plans  Assign Health Plan Attributes
Insurance Plans:
In this step, you define general data for insurance plans
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Insurance Plan General Data
Coverage Variants:
In this step, you define coverage variants to determined which factors influence the coverage an employee is entitled to in a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual coverage in this step. You simply define how coverage varies according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define coverage variants, you need to do the following:
1. Determine how often coverage varies for different coverage options.
This indicates how many coverage variants you need. Note the following:
u2022 If a plan has set coverages (including salary multiples), you need a
coverage variant for each.
u2022 If a plan allows employees to choose any amount of coverage within a
range, you need only one coverage variant.
u2022 If a plan has options, you will need a coverage variant for each option.
2. Determine how coverage varies according to employee data.
This determines how you need to set up your variants using employee groupings. For each variant, you can specify a parameter group and coverage grouping to determine coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans 
Coverage Rules:
In this step, you define the actual coverages for a plan.
You need to define coverage for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
Coverage can be defined as a flat amount or as a factor of salary
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Coverage Rules
Cost Variants:
In this step you define cost variants to determine which factors influence the cost of an insurance plan for an employee. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual costs in this step. You simply define how costs vary according to:
u2022 Plan
u2022 Coverage option
u2022 Employee data
Before you start to define cost variants, you need to do the following:
1. Determine how often cost varies for different coverage options:
u2022 If an insurance plan has set flat coverage options and flat costs, you need
to define a cost variant for each flat cost.
u2022 If you have set flat coverage options and the flat costs are directly
proportional to the coverage stated in the flat cost, you need only one
cost variant.
u2022 If an employee can choose any amount of coverage within a range and the
cost of the coverage is directly proportional to the coverage, you need
only one cost variant.
2. Determine how costs vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and cost grouping to determine cost. You can also indicate whether the gender of employees and whether or not they are smokers are cost criteria
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Variants
Cost Rules:
You need to define costs for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Define Cost Rules
Insurance Plan Attributes:
In this step, you bring together all those parts of an insurance plan, that you have already defined in the previous few steps.
You define the insurance plan options, then associate to each insurance plan:
u2022 Cost variant
u2022 Coverage variant
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Assign Insurance Plan Attributes
Combined Coverage Limits:
When you define coverages for plans such as insurance, you can set limits on the coverage amount. This is often used when the coverage is an amount dynamically calculated when the employee chooses her coverage.
However these limits apply only to one plan and yet you might need to define limits which combine the coverages of more than one plan.
In this chapter, you define these combined limits as follows:
1. The limit that might span 2 or more plans is reduced to a mathematical equation, where there is an amount on one side and plan coverages on the other side. The two sides of this equation are then DIVIDED BETWEEN the two views in this chapter.
2. The first view defines the limit in monetary terms which is one side of the equation. It also defines the operator (equals, is greater than, and so on).
3. The second view defines the other side of the equation in terms of the plan coverages
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Combined Coverage
Combined Coverage Limit Expressions:
In this step, you enter the second half of the equation, as discussed in combined coverage
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Define Combined Coverage Limit Expressions
Imputed Income for Selected Benefits:
In this section of the IMG, you define the criteria needed to calculate Imputed Income.
Imputed Income is based upon benefits paid for by the employer and calculated using rates set by the Internal Revenue Service (IRS). This value is then treated as taxable income for the employee
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Age Groups for Imputed Income
Review Calculation Factors for Imputed Income:
In this step, you check that the Imputed Income Rate Table entries are correct.
The imputed income age groups are associated with the rates/factors set by the IRS
IMG Path: Personnel Management  Benefits  Plans  Insurance Plans  Combined Coverage  Review Calculation Factors for Imputed Income
Savings Plans:
In this step, you define general data for savings plans.
You have defined the relevant type, status, and provider for each plan in the Basic Settings section of the Benefits IMG
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Savings Plan General Data
Employee Contribution Variants:
In this step you define employee contribution variants to determine which factors influence the permitted employee contribution to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contributions in this step. You simply define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employee contribution grouping to determine employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Variants
Employee Contribution Rules:
In this step, you define the employee contribution limits for each plan.
You need to define employee contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define minimum and maximum employee contribution in the following ways:
u2022 As a fixed amount
u2022 As a percentage of salary
u2022 As a contribution unit
In Payroll, the total employee contribution is the sum of these amounts
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employee Contribution Rules
Employer Contribution Variants:
In this step you define employer contribution variants to determine which factors influence the contribution the employer makes to a plan. Variants are plan-specific; each plan has its own variant(s).
You do not enter any actual contribution in this step. You only define how contributions vary according to:
u2022 Plan
u2022 Option (only for plans in the plan category Miscellaneous)
u2022 Employee data
Before you start to define variants, you need to do the following:
1. Determine how often employee contributions vary for plans and any plan options.
This indicates how many contribution variants you need.
2. Determine how employee contributions vary according to employee data.
This determines how you need to set up your variants using employee groupings.
For each variant, you can specify a parameter group and employer contribution grouping to determine employer contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Variants
Employer Contribution Rules:
In this step, you define limits for the contributions made by the employer to employee plans. You so this for each employer contribution variant for each plan.
You need to define employer contributions limits for each possible combination of employee grouping in the criteria you have attributed to each variant. If you have not specified any criteria in a variant, you assign one rule only.
You can define the employer contribution and the contribution limit in either of the following ways:
u2022 As a fixed amount / as an amount per unit contributed by the employee
u2022 As a percentage of employee base salary or employee contribution
IMG Path: Personnel Management  Benefits  Plans  Savings Plans  Define Employer Contribution Rules
Assign Savings Plan Attributes:
In this step, you complete the definition of savings plans by bringing together the relevant elements that you have already defined:
u2022 EE contribution variant
u2022 ER contribution variant

Differences between an InfoCube and ODS object

Hello All,
I am always hearing that an ODS overwrites data while a cube adds data loaded, and an ODS is a flat table etc.
Does anyone have a comprehensive document/article on how they differ so that I can be weary when doing data loads etc and be in a better position to not make a mistake when deleting data out of the targets etc, especially since financial data is so sensitive.
Thank you and kind regards,
Keith Kibuuka

Hi Keith,
I found below data on another site..
The most important difference between ODS and BW is the existence of key fields in the ODS. In the ODS you can have up to 16 info objects as key fields. Any other info objects will either be added or overwritten! So if you have flat files and want to be able to upload them multiple times you should not load them directly into the info cube, otherwise you need to delete the old request before uploading a new one. There is the disadvantage that if you delete rows in the flat file the rows are not deleted in the ODS.
I also use ODS-Objects to upload control data for update or transfer routines. You can simply do a select on the ODS-Table /BIC/A<ODSName>00 to get the data.
ODS is used as an intermediate storage area of operational data for the data ware house . ODS contains high granular data . ODS are based on flat tables , resulting in simple modeling of ODS .
we can cleanse transform merge sort data to build staging tables that can later be used to populate INOFCUBE .
Thanks
An infocube is a multidimentionsl dat acontainer used as a basis for analysis and reporting processing. The infocube is a fact table and their associated dimension tables in a star schema. It looks like a fact table appears in the middle of the graphic, along with several surrounding dimension tables. The central fact is usually very large, measured in gigabytes. it is the table from which you retrieve the interesting data. the size of the dimension tables amounts to only 1 to 5 percent of hte size of the fact table. common dimensions are unit & time etc. There are different type of infocubes in BW, such as basic infocubes, remote infocubes etc.
An ODS is a flat data container used for reporting and data cleansing/quality assurance purpose. They are not based on star schema and are used primaily for detail reporting rather than for dimensional analyais.
An infocube has a fact table, which contains his facts (key figures) and a relation to dimension tables. This means that an infocube exists of more than one table. These tables all relate to each other. This is also called the star scheme, because the dimension tables all relate to the fact table, which is the central point. A dimension is for example the customer dimension, which contains all data that is important for the customer.
An ODS is a flat structure. It is just one table that contains all data.
Most of the time you use an ODS for line item data. Then you aggregate this data to an infocube.
cheers,
Vishvesh

Difference between account based and cost based in co-pa

hi friends,
what is main deffirencebetween account based and cost based in co-pa. what scenerio we use account based and what scenerio we use cost based.
Thanking u
suneel.

Hi,
It all depends on the OPerating oncern which you are going to use for the CO-PA implementaion.
For a account based Operating concern you can define accopund based copa.
For a Cost Based Operating concdern you will have tp define account based Copa.
You can create account based Copa on cost based operating concern and vice versa.
In most of the FI implemntaion is done before BW inplemetation and therefore Operating concerns are already defined by the FI people.
Thanks
Message was edited by:
Ajeet Singh

Difference between GL Account and Cost Element associated

Hi,
In the system ECC6.0, due to modification it happens that there are some difference in the description between some GL account and their associated cost element.
Is there any way to have an automatic update in order to avoid this kind of problem.
Regards,
MAtthieu

Hi Matthieu,
Take a look at the OSS note 634887 and upload in your system the programs mentioned there.
With the program ZKA_KSTAR_TEXTS_INS_AND_UPD you are aible to update the cost element texts copying the corresponding G/L description
Kind regards,
Dan

Difference between Classic Planning and EPMA Application 11.1.2.2

what is the major variaine between Classic and EPMA Planning
Please advise

one works well and one is a lifetime of pain... let you decide which is which
See the search up on the right, put in the following
difference classic epma
and go to the results, where would we be without search engines.
Also do you ever get the feeling of Deja Vu - 11.1.2.1 Classic Planning vs EPMA Planning
Cheers
John
http://john-goodwin.blogspot.com/

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

Difference between business area and costcenter

Hi All,
Could u pls let me know the differences between Business Area and Cost Center.
Awaiting ur valuable responses.
Thanks & Regards
Chennuri

Hi,
i am giving a realtime information on business areas and cost centers.
For our company we have 25 branches. in sap we treat all of our branches as a seperate business area. the reason why we maintain business area. at the month end or year end financial statemensts are generated on company code basis and business area base. so we consider branches as a business area.
Cost center is like a cost object.
Hope this is clear,
Regards,
Sankar

Difference between partner order and partner oject?

hi all,
Can any one please explain the difference between partner order and partner object?
What is the purpose of partner object from controlling perspective?
Thanks in advance,
Regards,
S.Sumana.

Hi Kumar,
coming to customization in between SO(Rush order) and OR(Standard order).
Go to VOV8 T.Code.
The Rush order has the details as "Under Shipping tab",
There will be "X" mark in the immediate delivery .
the Rush order will be having the order related billing.
But the Standard order can be either Order related or Delivery related.
In Standard order after creating the order we are going to create the order we are going to create the delivery by using "VL01n" T.Code.After that we are going to create the billing by using "VF01" T.Code.
Regards,
Mohan.
I think you understood if you need any other info. pls ask.

Difference between COPC planning and cost object controlling

Similar Messages

Maybe you are looking for