Difference between TECO and CLSD in internal order/WBS

Hi friends,
Can anyone please tell me what is the difference between These two status TECO[Technically Complete] and CLSD [Closed] in internal order/WBS elements.
Thanks
Wilson

Hi,
Good morning and greetings,
The term TECO stands for Technically Completed and this status is activated to do month end settlements to the IO so that costs accumulated till that point would be compared against the planned cost and would be settled for difference... The TECO status would be revoked after the month end to continue for further collecting of costs and would be settled finally...Once you invoke the status CLSD the system will not allow you to post any more further postings to the internal order.
Please reward points if found useful
Thanking you
With kindest regards
Ramesh Padmanabhan

Similar Messages

DIFFERENCE BETWEEN TECO AND CLOSED

What is the difference between teco and closed?

Dear Debasish,
check this.
For TECO Status:
The following actions are executed if an order is set to Technically complete.
The order is not relevant for MRP planning
Reservations are deleted
Capacity requirements are deleted
Purchase requisitions for external operations or non-stock materials are deleted
The order and its operations receive the system status Technically Completed (TECO)
If an order is technically complete, you cannot change it. The fields in the order
are displayed but cannot be changed. You can however cancel technical
completion, for instance if order data has to be changed.
For Closed Status:
The Closed (CLSD) status has been introduced in the production order. It has the following characteristics:
No more costs can be posted to the order, that is, confirmations and goods movements are no longer permitted for the order.
The order can no longer be changed. Exceptions to this are revoking the CLSD status and setting the deletion flag.
All actions relating to the status technically completed (TECO) are executed.
In a collective order, the CLSD status is also set for subordinate orders.
If the system comes across an order in the collective order that cannot be closed, the orders that come between this order and the leading order are also not closed. Other subtrees are closed if they only contain orders that can be closed.
Check this links for further understanding
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/a5/63198843a211d189410000e829fbbd/frameset.htm">closed status</a>
<a href="http://help.sap.com/saphelp_erp2005/helpdata/en/a5/63198843a211d189410000e829fbbd/frameset.htm">TECO</a>
Regards
Mangal

What is the difference between TECO and Order settlement?

What is the diff. between TECO and order settlement and what is the use of both?

Hi,
Technical completion means ending a production order from a logistical viewpoint. This function is usually used, if the execution of an order has to be stopped prematurely or if the order could not be executed in the required manner and open requirements for the order (reservations, capacities) should be deleted.
Where as Settlement of an order is carried out periodically to settle the costs related to the order to a settlement receiver.
for more details read
http://help.sap.com/saphelp_46b/helpdata/en/a9/ab7422414111d182b10000e829fbfe/frameset.htm
and
http://help.sap.com/saphelp_46b/helpdata/en/a3/664a3397e311d1b5a70000e8359890/frameset.htm
Regards,
Sumeet

DIFFERENCE BETWEEN TECO AND LOCK

Will u kindly tell me the difference between Technically Complete(TECO) and Locking

Dear Mr.Deabsish,
Check this content which's taken from sap.help
Technical completion means ending a production order from a logistical viewpoint. This function is usually used, if the execution of an order has to be stopped prematurely or if the order could not be executed in the required manner and open requirements for the order (reservations, capacities) should be deleted.
Prerequisites
The Technically complete function must be allowed for the operation, that is, it cannot be disallowed due to a system or user status.
The following actions are executed if an order is set to Technically complete.
The order is not relevant for MRP planning
Reservations are deleted
Capacity requirements are deleted
Purchase requisitions for external operations or non-stock materials are deleted
The order and its operations receive the system status Technically Completed (TECO)
If an order is technically complete, you cannot change it. The fields in the order are displayed but cannot be changed. You can however cancel technical completion, for instance if order data has to be changed.
After technical completion you can still make postings for the order. For instance, material withdrawal or a confirmation can be posted if they were previously forgotten.
Activities
You can execute this function in two ways:
When you are changing an order, choose Functions - Restrict processing - Technically complete.
Technically complete is a function that you can use in mass processing.
You can reverse technical completion as follows:
When you are changing an order, choose Functions - Restrict processing - Revoke technical completion.
Reward points & close this thread.
Regards
Mangal

Difference between Valuated and Non valuated Sale order stock

Hi All,
Can anybody tell me the difference between the above said subject with the steps involved in each scenario.
That is valuated sale order stock and Non valuated sale order stock in Product cost by Sale Order.
With Journal entries at each step and whether any WIP or variances at Production order level and sale order level and all the financial entries related to them
Thanks in Advance,
Ravi Kumar

Hi Shail,
Thans for your inputs,
But I wanted to know it in more detail. In what scenarios they are used with financial entries in both the cases.
I will give you my scenario. It goes like this,
My client is in pipe coating business, who receives pipes from customers and does only coating work(which is considered as service) and despatches it to the customer. this process is carried on the basis of work order(Sale order).
Now Production order is created and work is done on that with reference to Sale order for that particular customer.
So the pipe which my client receives should be non valuated stock as it will not be a raw material to them and the cost incurred on it is booked on production order like chemicals as raw material consumption, activity cost etc.
now in this scenario just tell me how and at which stage FI entries get generated at Production order and Sale order level, and also at wat level Standard cost estimate should be created i,e at production order level or sale order level(sale order cost estimate).
Will there be any entries at goods isssue and GR against production order. If no then how the COGM account will get hit.
Please tell me this scenario in both cases Valuated sale order stock and Non valuated sale order stock with financial entries in Sale order costing.
Thanks & Regards,
Ravi Kumar

Difference between techo and close order

Dear all
plz tell what is a difference between techo and close production order
guide me
Rgds
SDB
Edited by: surendra patil on Aug 21, 2008 12:18 PM

TECO means ending a production order from a logistical viewpoint. This function is usually used, if the execution of an order has to be stopped prematurely or if the order
could not be executed in the required manner and open requirements for the order (reservations,capacities) should be deleted.
The following actions are executed if an order is set to TECO:
· The order is not relevant for MRP planning
· Reservations are deleted
· Capacity requirements are deleted
· Purchase requisitions for external operations or non-stock materials are deleted
· The order and its operations receive the system status (TECO)
If an order is technically complete, you cannot change it. The fields in the order are displayed but
cannot be changed. You can however cancel technical completion, for instance if order data has
to be changed.
After technical completion you can still make posting for order.
For instance,material withdrawal or a confirmation can be posted if they were previously forgotten.
*Closed Order :
*The Closed (CLSD) status has been introduced in the production order. It has the following
characteristics:
· No more costs can be posted to the order, that is, confirmations and goods movements are
no longer permitted for the order.
· The order can no longer be changed. Exceptions to this are revoking the CLSD status and
setting the deletion flag.
· All actions relating to the status technically completed are executed
· In a collective order, the CLSD status is also set for subordinate orders.
· If the system comes across an order in the collective order that cannot be closed, the orders
that come between this order and the leading order are also not closed. Other subtrees are
closed if they only contain orders that can be closed.
Regards,
Hrishi.

Sales order - difference between Cancel and Close?

Hi All,
In Sales Order, is there any differences between Cancelling order and Closing order?
Thanks
Ric

Hi Ric...........
Difference between Cancel and close means if you raised Sales Order and your terms and condition is not accepted by your customer in such situation you have to cancel your order.
if you raised Sales Order and you did not agree with the payment terms sent by your customer in such situation you have to cancel your order.
if you raised Sales Order and put a date on which sale order should be canceled automatically if its not proceeded further from your customer in such situation you have to cancel your order.
But order cancellation must be before raising and type of target document.
Order close means if you have already raised target document against SO and now before completing order you have to stop the transactions or as per the validity of the Sales Contract then in such case you have to close the document......
Hope this is sufficient to know the difference between those....
Regards,
Rahul

How to create a service order and check the internal order in R/3

Required Solution:
1. How to copy existing service order and create new one and check the internal order in R/3, whether the certain service order is correctly created in r/3, can you polease explain the steps plz.
2. If i am creating service order by service template finally the service order is getting created but it is not showing me in the table iaom_crm_aufk, how to check this.
can any one help me in this issues as soon as possible.

Hello Zita,
Try to restart your portal after creating ServiceUser in both UME and KM.
One more major difference between ServiceUser and normal portal user is that a ServiceUser does not have a UserAccount (IUserAccount)
Object serviceContext = null;
 try {
 serviceContext = AccessController.doPrivileged(new PrivilegedExceptionAction() {
 public Object run() throws WcmException {
 return ResourceFactory.getInstance().getServiceContext(CONTRACT_SERVICE_USER);
 } catch (PrivilegedActionException e) {
 logger.severe(e, "ResourceContext for the technical " + serviceUser +
 " user could not be retrieved.");
IResourceContext resCtx = (IResourceContext) serviceContext;
So I modify all KM resources with this resCtx.
Hope this helps ...
Greetings,
Praveen Gudapati
p.s. Points are always welcome for helpful answers

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

Difference between Distribution and Assessment cycle

Hi,
Can any one help me regarding the above(Difference between Distribution and Assessment cycle)
Thanks in advance
Rajani

HI,
Assessment:
Assessment was created to transfer primary and secondary costs from a sender cost center to receiving controlling objects. During assessment, cost centers or business processes can be used as senders .n The receivers for an assessment can be a cost center, WBS element, internal order, cost object, or a
business process. You can restrict the number of receiver categories in customizing. n Primary and secondary postings are allocated at the end of the period by means of the user-defined
key.
n During assessment, the original cost elements are summarized into assessment cost elements
(secondary cost element category = 42). As the system writes fewer totals records, the assessment
has a better performance than periodic reposting and distribution.
n Line items are posted for the sender as well as for the receiver, enabling the allocation to be recorded
exactly. The system does not display the original cost elements in the receivers. Therefore,
assessment is useful if the cost drilldown for the receiver is not important, for example, as in the case
of the allocation for the "cafeteria" cost center.
n Similar to distribution, the partner is updated in the totals record during distribution.
n You can reverse assessments as often as required.
n You use the Cycle -Segment method to define sender-receiver relationships.
Distribution:
Differences between periodic reposting and distribution are due to information content and
performance.
n For periodic reposting, no separate credit record is written on the sender for the cost element in the
summary report. Instead, the totals record for the cost element is reduced on the debit side, which
means that the original debit amount can no longer be checked there ("unclean credit"). However,
during distribution, the system writes a totals record for the credit ("clean credit"). The information
on the receiver is the same for periodic reposting and distribution ("clean debit").
n Compared with periodic reposting, during distribution, the system also updates the partner in the
totals record for the sender. This means that the partner can be displayed in the information system
on the totals record level.
n As fewer totals records are written during periodic reposting, performance is better than during
distribution. See customizing for an example with figures that illustrates this aspect. Under utilities,
make settings for the SAPscript text display, then call up the text by choosing Periodic reposting,
Distribution, or Assessment from the menu.
Regards,
Meenakshi

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 ASSESSMENT AND DISTRIBUTION

Dear Friends,
What is the main difference between Assesment and Distribution?
Thanks in advances.

Hello,
Please follow the forum rules
1. No capital letters
2. Search before posting
DISTRIBUTION =========== Distribution was created for transfer primary costs from a sender cost center to receiving controlling objects. During distribution, only cost centers or business process can be used as sender. A distribution receiver can be a cost center, WBS element, internal order, cost object, or a business process. You can restrict the number of receiver categories in customizing. Primary Postings (such as, energy costs) are collected on a cost center, and allocated at the end of the period by means of the user-defined key. You can only distribute primary costs. During this process, the original cost element remains the same. Line items are posted for the sender as well as for the receiver, enabling the allocation to be recorded exactly. You can reverse distributions as often as required. You use the Cycle-Segment method to define sender-receiver relationships. PERIODIC REPOSTING ================= Differences between periodic reposting and distribution are due to information content and performance. For periodic reposting, no separate credit record is written on the sender for the cost element in the summary report. Instead, the totals record for the cost element is reduced on the debit side, which means that the original debit amount can no longer be checked there (u201Cunclean creditu201D). However, during distribution, the system writes a totals record for the credit (u201Cclean creditu201D). The information on the receiver is the same for periodic reposting and distribution (u201Cclean debitu201D). Compared with periodic reposting, during distribution, the system also updates the partner in the totals record for the sender. This means that the partner can be displayed in the information system on the totals record level. As fewer totals records are written during periodic reposting, performance is better than during distribution. ASSESSMENT =========== Assessment was created to transfer primary and secondary costs from a sender cost center to receiving controlling objects. During assessment, cost center or business processes can be used as senders. The receivers for an assessment can be a cost center, WBS element, internal order, cost object, or a business process. You can restrict the number of receiver categories in customizing. Primary and secondary posting are allocated at the end of the period by the user-defined key. During assessment, the original cost elements are summarized into assessment cost elements (secondary cost element category = 42). As the system writes fewer total records, the assessment has a better performance than periodic reposting and distribution. The system does not display the original cost elements in the receivers. Therefore, assessment is useful if the cost drilldown for the receiver is not important. Similar to distribution, the partner is updated in the totals record during distribution You can reverse assessments as often as required. You use the Cycle-Segment method to define sender-receiver relationships. Regards, Ravi

Difference between VMI and collaboration with customer

Hai,
I am trying to understand the difference between VMI and collaborative planning with customer(CPC)
Please correct me if I am wrong. In VMI, a vendor or manufacturer sells his material to customer and through EDI, the customer gives the information such as forecast, stock etc.
In CPC, the vendor and customer interchange information, such as demand, stock levels, promotions, delivery dates etc., based on ITS.
What is the difference between these two?
If I am not wrong, EDI is used for outside company communication andITS for within. So, can I say that VMI is for customer outside the company and CPC for internal customer?
Thank you.

Hi Visu,
Service provided by a vendor for a customer, whereby the vendor plans material requirements in the customer's company. Vendor-managed inventory is only possible if the vendor has access to the customer's current stock and sales data.
In the ERP system, the following functions are available for vendor-managed inventory:
Transfer of stock and sales data by EDI
Receipt of stock and sales data by EDI
Replenishment planning for customers
Creation of a purchase order for an external EDI order acknowledgment
supply chain management tool that synchronizes demand signals and supply chain activities by utilizing Internet technology. Collaborative Planning enables supply chain partners to view, share and synchronize common information within the supply chain.
Hope this helps.
Regards,
Mohan

Difference between 0PM_OM_OPA_1 and 0PM_PRM_PLCS_1

Hello,
Can you pls provide me information about difference between 0PM_OM_OPA_1 and 0PM_PRM_PLCS_1 data sources?
Both of them extract plan data.
Regards,
Romano

Hi,
0PM_PRM_PLCS_1 - This DataSource is used to load the movement data for maintenance planned costs.
Prerequisites
Configure the desired extraction parameters in the TPM_C05 Customizing table (transaction SM30).
Parameters for the Costing of Maintenance Task Lists
·        Reference date for the costing
·        Order type for the costing
·        Package size for the internal subdivision of the extraction
Parameters for the Costing of Maintenance Plans
·        Reference time for the costing
·        Package size for the internal subdivision of the extraction
whereas Only full upload for DataSource 0PM_OM_OPA_1
-Vikram

What is the difference between MOVE and WRITE TO ststement?

Hi
What is the difference between MOVE and WRITE TO ststement?
When do we use both of them?
Thank You

Hi,
MOVE
Syntax
MOVE source {TO|?TO} destination.
destination {=|?=} source.
Effect
Both these statements assign the content of the operand source to the data object destination. The variants with the language element TO or the assignment operator = are valid for all assignments between operands that are not reference variables, and for assignments between reference variables for which the static type of source is more specific than or the same as the static type of destination(narrowing cast).
Variants with the language element ?TO or the assignment operator ?= (casting operator ) must be used if the source and destination are reference variables and the static type of source is more general than the static type of destination (widening cast). For assignments between operands that are not reference variables, use of the question mark ? is not permitted.
The data object destination can be any data object that can be listed at a write position, and the data object source can be a data object, a predefined function or a functional method (as of release 6.10). The data type of the data object destination must either be compatible with the data type of source, or it must be possible to convert the content of source into the data type of destination according to one of the conversion rules.
Notes
If source and/or destination are field symbols, then, as in all ABAP commands, the system works with the content of the data objects to which the field symbols point. The actual pointer content of a field symbol can only be changed using the statement ASSIGN or the addition ASSIGNING when processing internal tables (value semantics). If source and destination are reference variables, the reference contained in source is assigned to destination (reference semantics).
Strings and internal tables are addressed internally using references. When assignments are made between strings and between internal tables (as of release 6.10), only the reference is transferred, for performance reasons. After the assignment, the actual string or the actual table body of the source as well as the target object are addressed (sharing). When the object is accessed to change it, the sharing is canceled and a copy of the content is made. The sharing is displayed in the memory consumption display of the ABAP debugger and in the Memory Inspector tool (as of release 6.20).
Obsolete Form: MOVE PERCENTAGE
Exceptions
Catchable Exceptions
CX_SY_CONVERSION_NO_NUMBER
Cause: Operand cannot be interpreted as number
Runtime Error: CONVT_NO_NUMBER (catchable)
CX_SY_CONVERSION_OVERFLOW
Cause: Overflow with arithmetic operation (type P, with specified length)
Runtime Error: BCD_FIELD_OVERFLOW (catchable)
Cause: Operand too large or (intermediate) result too large
Runtime Error: CONVT_OVERFLOW (catchable)
CX_SY_MOVE_CAST_ERROR
Cause: Source or target variable are not reference variables
Runtime Error: MOVE_CAST_REF_ONLY
Non-Catchable Exceptions
Cause: Source field (type P) does not contain correct BCD format.
Runtime Error: BCD_BADDATA
Cause: Assignment for deep structures not permitted if these overlap.
Runtime Error: MOVE_COMPLEX_OVERLAP
Cause: Type conflict with the assignment between object references.
Runtime Error: MOVE_INTERFACE_NOT_SUPPORTED,
Runtime Error: MOVE_IREF_NOT_CONVERTIBLE,
Runtime Error: MOVE_IREF_TO_OREF,
Runtime Error: MOVE_OREF_NOT_CONVERTIBLE
Cause: Type conflict with the assignment between data references.
Runtime Error: MOVE_DREF_NOT_COMPATIBLE
Cause: Assignment between the types involved not supported.
Runtime Error: MOVE_NOT_SUPPORTED
Cause: Constants and literals must not be overwritten.
Runtime Error: MOVE_TO_LIT_NOTALLOWED
Cause: onstants and literals must not be overwritten.
Runtime Error: MOVE_TO_LIT_NOTALLOWED_NODATA
Cause: During a loop in an internal table, an attempt was made to overwrite a reference variable that is linked with the internal table by REFERENCE INTO.
Runtime Error: MOVE_TO_LOOP_REF
Write
Syntax Diagram
WRITE - TO
Syntax
WRITE {source|(source_name)} TO destination
 [int_format_options].
Effect:
This statement assigns the formatted content of the data object source, or the formatted content of the data object whose name is contained in source_name, to the data object destination. The data objects source_name and destination must be character type and flat. source_name can contain the name of the data object to be assigned in upper or lower case. If the data object specified in source_name does not exist, the assignment is not executed, and sy-subrc is set to 4.
The statement WRITE TO has the same effect as the statement WRITE for lists. This statement formats the content of source or the source field specified in source_name as described in the field. It does not, however, store the result in an output area of a list in the list buffer, but instead stores it in a variable. The output length is determined by the length of the variable.
The same additions int_format_options can be specified for formatting the content as in the statement WRITE for lists, except for NO-GAP and UNDER.
System fields
sy-subrc Meaning
0 The data object specified in source_name was found and the assignment was executed.
4 The data object specified in source_name was not found and the assignment was not executed.
For the static specification of source, sy-subrc is not set.
Note:
If destination is specified as an untyped field symbol or an untyped formal parameter, and is not flat and character-type when the statement is executed, this leads to an untreatable exception in a Unicode program. In non-Unicode programs, this only leads to an exception for deep types. Flat types are handled as character-type data types.
Example:
After the assignment, the variables date_short and date_long receive the current date in the order specified in the user master record. The variable date_long also contains the defined separators, as the output length is sufficiently long. The content of the variable date_mask is formatted according to the formatting addition DD/MM/YY.
DATA: date_short(8) TYPE c,
 date_long(10) TYPE c,
 date_mask(8) TYPE c.
WRITE sy-datum TO: date_short,
 date_long,
 date_mask DD/MM/YY.
Exceptions
Non-Catchable Exceptions
Cause: Negative length specified for offset/length
Runtime Error: WRITE_TO_LENGTH_NEGATIVE
Cause: Negative offset specified in offset/length
Runtime Error: WRITE_TO_OFFSET_NEGATIVE
Cause: Offset specified in offset/length specification is longer than the field length.
Runtime Error: WRITE_TO_OFFSET_TOOLARGE
Thanks
sunil

Difference between TECO and CLSD in internal order/WBS

Similar Messages

Maybe you are looking for