Difference between Full settlement & periodic settlement

What is Difference between Full settlement & periodic settlement, & how these works works on orders. Can anyone tell me that how can I check result for the same. (Kindly mention t-codes also)
Regards.....Kaushal

Hi,
Please find below some salient features of each os the settlement type you have asked for:
1. Periodic settlement -
a) Will have Product cost collector as cost object (both REM and Descrete scenarios)
b) WIP and scrap variances are based on Target costs
c) Variances are recognized in the month in which they are actually incurred based on the target costs. Varainces = Total costs - GR - Target WIP
d) Default rule in OPL8 should be periodic settlement
2. Full Settlement
a) Manufacturing orders will be costs objects
b) WIP will be at actuals. WIP = Total costs - GR value
c) Varainces will be recognised only when the order is fully delivered. till that time though there are variances, they will not be recognized but will be included in WIP value. This is the key aspect of Full Settlement
d) Default Rule in OPL8 would be full settlement
T.codes relevant:
KSV5     Run dist cycle
KSU5     Run assessment cycle
KSUB     Run assessment cycle
KEU5     Run COPA assessment cyle
KKA0     Change Cutoff Period for WIP
KKAS/KKAX     WIP - Individual Processing
KKAO     WIP - Collective Processing
KKS6/KKS2     Variance Calculation - Individual
KKS5/KKS1     Variance Calculation - Collective
KK87/KO88     Settlement - Individual
CO88     Settlement - collective
*For Sale Order controlling     *
KKA3     Execute Result Analysis - Individual
KKAK     Execute Result Analysis - Collective
VA88     Sale Order Settlement
Best Regards
surya

Similar Messages

EXACT DIFFERENCE BETWEEN FULL LOAD AND REPAIRFULL LOAD?

HI Champ,
Can anyone explain me the exact difference between full load and Repairfull load?Give e some senario where we can go for this?Please.....
10zin

Hi,
Full repair can be said as a Full with selections. But the main use or advantage of Full repair load is that it wont affect delta loads in the system. If you load a full to a target with deltas running you again will have to initialize them for deltas to continue. But if you do full repair it wont affect deltas.
This is normally done we when we lose some data or there is data mismatch between source system and BW.
Check the OSS Note 739863 'Repairing data in BW' for all the details
Symptom
Some data is incorrect or missing in the PSA table or in the ODS object (Enterprise Data Warehouse layer).
There may be a number of reasons for this problem: Errors in the relevant application, errors in the user exit, errors in the DeltaQueue, handling errors in the customers posting procedure (for example, a change in the extract structure during production operation if the DeltaQueue was not yet empty; postings before the Delta Init was completed, and so on), extractor errors, unplanned system terminations in BW and in R/3, and so on.
Solution
Read this note in full BEFORE you start actions that may repair your data in BW. Contact SAP Support for help with troubleshooting before you start to repair data.
BW offers you the option of a full upload in the form of a repair request (as of BW 3.0B). If you want to use this function, we recommend that you use the ODS object layer.
Note that you should only use this procedure if you have a small number of incorrect or missing records. Otherwise, we always recommend a reinitialization (possibly after a previous selective deletion, followed by a restriction of the Delta-Init selection to exclude areas that were not changed in the meantime).
1. Repair request: Definition
If you flag a request as a repair request with full update as the update mode, it can be updated to all data targets, even if these already contain data from delta initialization runs for this DataSource/source system combination. This means that a repair request can be updated into all ODS objects at any time without a check being performed. The system supports loading by repair request into an ODS object without a check being performed for overlapping data or for the sequence of the requests. This action may therefore result in duplicate data and must thus be prepared very carefully.
The repair request (of the "Full Upload" type) can be loaded into the same ODS object in which the 'normal' delta requests run. You will find this request under the "Repair Request" option in the InfoPackage (Maintenance) menu.
2. Prerequisites for using the "Repair Request" function
2.1. Troubleshooting
Before you start the repair action, you should carry out a thorough analysis of the possible cause of the error to make sure that the error cannot recur when you execute the repair action. For example, if a key figure has already been updated incorrectly in the OLTP system, it will not change after a reload into BW. Use transaction RSA3 (Extractor Checker) in the source system for help with troubleshooting. Another possible source of the problem may be your user exit. To ensure that the user exit is correct, first load a user exit with a Probe-Full request into the PSA table and check whether the data is correct. If it is not correct: Search for the error in the exit user. If you do not find it, we recommend that you deactivate the user exit for testing purposes and request a new Full Upload. It If the data arrives correctly, it is highly probable that the error is indeed in the user exit.
We always recommend that you load the data into the PSA table in the first step and check the result there.
2.2. Analyze the effects on the downstream targets
Before you start the Repair request into the ODS object, make sure that the incorrect data records are selectively deleted from the ODS object. However, before you decide on selective deletion, you should read the Info Help for the "Selective Deletion" function, which you can access by pressing the extra button on the relevant dialog box. The activation queue and the ChangeLog remain unchanged during the selective deletion of the data from the ODS object, which means that the incorrect data is still in the change log afterwards. After the selective deletion, you therefore must not reconstruct the ODS object if it is reconstructed from the ChangeLog. (Reconstruction is usually from the PSA table but, if the data source is the ODS object itself, the ODS object is reconstructed from its ChangeLog). You MUST read the recommendations and warnings about this (press the "Info" button).
You MUST also take into account the fact that the delta for the downstream data targets is created from the changelog. If you perform selective deletion and then reload data into the deleted area, this may result in data inconsistencies in the downstream data targets.
If you only use MOVE and do not use ADD for updates in the ODS object, selective deletion may not be required in some cases (for example, if incorrect records only have to be changed, rather than deleted). In this case, the DataMart delta also remains intact.
2.3. Analysis of the selections
You must be very precise when you perform selective deletion: Some applications do not provide the option of selecting individual documents for the load process. Therefore, you must first ensure that you can load the same range of documents into BW as you would delete from the ODS object. This note provides some application-specific recommendations to help you "repair" the incorrect data records.
If you updated the data from the ODS object into the InfoCube, you can also delete it there using the "Selective deletion" function. However, if it is compressed at document level there and deletion is no longer possible, you must delete the InfoCube content and fill the data in the ODS object again after repair.
You can only perform this action after a thorough analysis of all effects of selective data deletion. We naturally recommend that you test this first in the test system.
The procedure generally applies for all SAP applications/extractors. The application determines the selections. For example, if you cannot use the document number for selection but you can select documents for an entire period, then you are forced to delete and then update documents for the entire period in the data target. Therefore, it is important to look first at the selections in the InfoPackage exactly before you delete data from the data target.
Some applications have additional special features:
Logistics cockpit: As preparation for the repair request, delete the SetUp table (if you have not already done so) and fill it selectively with concrete document numbers (or other possible groups of documents determined by the selection). Execute the Repair request.
Caution: You can currently use the transactions that fill SetUp tables with reconstruction data to select individual documents or entire ranges of documents (at present, it is not possible to select several individual documents if they are not numbered in sequence).
FI: The Repair request for the Full Upload is not required here. The following efficient alternatives are provided: In the FI area, you can select documents that must be reloaded into BW again, make a small change to them (for example, insert a period into the assignment text) and save them -> as a result, the document is placed in the delta queue again and the previously loaded document under the same number in the BW ODS object is overwritten. FI also has an option for sending the documents selectively from the OLTP system to the BW system using correction programs (see note 616331).
3. Repair request execution
How do you proceed if you want to load a repair request into the data target? Go to the maintenance screen of the InfoPackage (Scheduler), set the type of data upload to "Full", and select the "Scheduler" option in the menu -> Full Request Repair -> Flag request as repair request -> Confirm. Update the data into the PSA and then check that it is correct. If the data is correct, continue to update into the data targets."
Refer.
Repair full request
Re: Repair full request
Steps to perform repair full request
full repair request
repair full request
Re: Repair Full Request
Thanks,
JituK

What's the difference between "Full Name" and "Account Name"

Just re-install a new OS X Lion. On the "Create Your Computer Account" screen, what's the difference between "Full Name" and "Account Name"?

Your computer name by default would be "John David Appleseed's Macbook Pro"
But you can always change that in System Preferences->Sharing
And yes, the first account you set up will be an administrator.

What is the difference between full checkpoint and incremental checkpoint?

What is the difference between full checkpoint and incremental checkpoint?
And what is checkpoint queue?
Can someone clarify these concepts?
Thanks!

Hi,
there are different types of checkpoints:
- Full checkpoint:
=> DBWR writes all dirty buffers from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
This is the setup point for SMON for a crash recovery.
- Partial checkpoint:
=> DBWR writes all dirty buffers of a singel tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- can e triggered by an ALTER TABLESPACE OFFLINE, ALTER TABLESPACE READ ONLY, ALTER TABLESPACE BEGIN BACKUP statement.
Incremental checkpoint:
number to all file headers and the controlfile.
-- can be triggered by different events, like a logswitch, a manual checkpoint (alter system ..), a shutdown and so on
- Partial checkpoint:
=> DBWR writes all dirty buffers of a single tablespace from the Buffer cache to the datafiles and CKPT retrieves a new Checkpoint Change Number from a sys owned sequence and writes this number to all file headers and the controlfile.
-- frequency is determined by FAST_START_MTTR_TARGET parameter (new feature to Oracle 9i), with wich you can specify a time in seconds which SMON is allowed to take maximal for a Crash Recovery until the database must be open again.
Dapending on the system you have SMON must calculate the maximum number of Redolog-blocks which it can manage to recover in the specified number of seconds. It will then create so called incremental checkpoints which will be tracked in the so called checkpoint queue in memory.
FAST_START_MTTR_TARGET is auto-tuned in Oracle 10g and Oracle tries to manage (incremental) checkpoint in a fashion that a minimum of I/Os are caused and a minimum time for crash recovery is needed.
If you set LOG_CHECKPOINTS_TO_ALERT to TRUE you will find checkpoint information in the alertSID.log file. You will see FULL and INCREMENTAL checkpoints then.
Hope this clarifies your question,
Lutz Hartmann

Difference between Full backup and lncremental level 0 backup

Hi,
What is the difference between Full backup and lncremental level 0 backup?
what I understand is:
Actually incremental backup backups all the block containing data and skips the blocks that are unused.
Similarly full backup backups all the blocks containing data.(does it skip unused blocks ?????).
The only difference that I feel is that the level 0 backup is recorded as an incremental backup in the RMAN repository, so it can be used as the parent for a level 1 backup where Full database backup is not recorded in the Rman respository and cannot be used as parent for level 1 backup.
(if you still feel you have some more points to share regarding the difference between backups, I request to share with me)
so my question here is
Can we use Incremental level 0 backup for full database recovery. Else is there any compulsion like we must only use full database backup for full database recovery?
can anyone throw light on this
with regards;
Boo

nowhere in this thread we talked about the image copies as we are only talking about the incremental backup.
The word "always" has a meaning. If you now wish to say, "well, RMAN will mostly use a level 0 or full backup, except when there are image copies around" then the word "always" doesn't fit your newly-revised description. That would make it an inappropriate word to use. And indeed, it's a factually wrong word to use.
If you want to get really picky about it, incidentally, the words 'datafile copy' appear in a post from me at Aug 4, 2007 6:03 PM whereas your post (in which the "always" word was used) only appears Aug 4, 2007 8:32 PM -a full 2 and a half hours (and and two posts) AFTER the concept of image copies had been mentioned.
But regardless of times: you can't just pretend image copies don't exist just because they haven't been mentioned so far in a thread. If you post "this is the way something ALWAYS works", you'd better be completely right about it, because "ALWAYS" is a big word. And there's no grey about this: either "always" is right, or it's wrong. And in this case, it's wrong: there are many times when RMAN will not do what you baldly asserted it would do. Image copies aren't some rare, exotic beast, either... so the occasions when your 'rule' breaks down are many and common.
until now I was simply beliving in what Oracle docs and metalink notes says
Try not to do that. Because you will fall into error after error if you do. Metalink is not the Holy Gospel of Oracle. Testing is, and it's because I've been testing this stuff since 1999 I will, on this occasion, decline your kind invitation to do "a small test". Been there, done that.
All of which leaves us discussing things that are of no relevance to the original poster, and I have no desire to take the thread off into silly areas of dispute. So I will leave it there, and I have nothing further to say on the matter. RMAN does what it does, and what it does is not what you said it would do. End of story.

Difference between data selection period and personal seletion period

Hi
Experts ,
ples Expline ,
Difference between data selection period and personal seletion period. to Data screening .

Data selection period means
For example if u given any period,
here we are checking whether data is valid in this period.
Personal selection period means
we are checking whether person is valid in a given period.
Example is:
For example if the employee resigned in a company on 15th of month.
He can get the salary only at the end of month it means his data is avilable upto end of month.
But when you consider his status from 16th to end of month
the person is not available.
So when u given date(16th to end of month) in data selection period is showing that person data is avilable.
But when mention that date in person selection period it is showing no person is avilable.
if useful
reward with points............

Difference between full DTP & delta DTP

hi experts,
will u pls explain wat is the exact difference between full DTP & delta dtp.
thanks,
sridhar

Hi Sridhar,
Adding to same.
If in PSA you have 2 request
e.g
Req 2 100 Rec
Req 1 200 Rec
Now First time you are running
If
FULL : All the 2 request will come to DSO
Req 2 100 Rec
Req 1 200 Rec
If
DELTA : All the 2 request will come to DSO
Req 2 100 Rec
Req 1 200 Rec
Now there is one more request comes in your PSA
e.g
Req 3 100 Rec
Req 2 100 Rec
Req 1 200 Rec
Now In case of
FULL LOAD : 3 Request will come in DSO
Req 3 100 Rec
Req 2 100 Rec
Req 1 200 Rec
In case of
DELTA LOAD : 1 Request will come in DSO
Req 3 100 Rec
Hope this will make your doubt clear.
Thanks
Mayank Singh Chauhan

What's the difference between full & large when importing video?

In my preference menu, it shows I can import video as either full-original size or large-960x540. Does it make a difference in the size of the file, in the quality of the view, in what can be done with the file? Also, can I determine whether I want it imported as a .mov or .dv or .iprojectimovie? Thanks

since vers08, it is a well-known fact, that iM can not handle interlaced material, there are tons of threads on this topic alone on this board. and it seems as though, that iM does a very 'simple' de-interlacing, by dropping one field: 1920x1080i => 1920x540'p'
I don't like to go into detail, but modern hardware, beyond tubes and arial broadcast, doesn't use, can not handle interlace, any flat-screen, computer or TV, de-interlaces anyhow.
so, if you need for any reason, that extra horizontal resolution, keep it full, otherwise use large.
lubrom wrote:
... I apologize for my ignorance but what is the difference between a container, a media wrapper, codec and folder structure?
sorry for my ignorance, but you asked for it ... ( ? )
lubrom wrote:
... can I determine whether I want it imported as a .mov or .dv or .iprojectimovie?

Difference between sales order, period, order

hi gurus,
can any one clarify my understanding as below said.
Sale order costing :
This means the standard costing is generated at the time of sale order creation with reference to (BOM & Routing). or standard cost can be generated even after sales order completion.
The only difference between Valuated & non valuated is that Goods issue to production order (Purchase order RAW material cost will be caputed in valuated, where current cost of RAW material will be captured for non valuated).
Period & Order:* This means standard costing with out reference to sale order.
Regads,
RAM

hi
check the following link
http://help.sap.com/saphelp_46c/helpdata/en/1d/39d448cd3011d19eb3080009b0db33/content.htm
You have very good explanation here
krishna

Whats the difference between full screen mode on iLife 09 and 11?

I had a overview of iLife 11 in store at Apple yesterday, I like the ful screen mode of it. I have iLife 09 but never really used it much to be honest.
I just fired it up, and it has a full screen mode on it I see, so whats the difference between '09 and '11 full screen version?
Also I'm a little worried if my iMac would run it fine? Its a 2007 Alu Core 2 Duo 2Ghz, 2Gb RAM, so a little older
cheers

If viewing full screen is your primary interest with iPhoto then iPhoto 11 may not be for you. iPhoto 11 has new themes for books, cards and slideshows which are rather slick and offers 2 page spread layouts in the books. In all fairness, it has had its difficulties as you can easily tell by the posts but not by everyone.
Bottom line: it all depends on what you primarily use iPhoto for. Excellent image management and organization or the frills, bells and whistles of its other features.
Happy Holidays

Difference between full and target quantity in iteme category

What is the difference between Target quantity and Full quantity in Completion rule in Item Catergory customization?

hi
full quantity is used for quotations
target quantity for contracts
Completion rules
An item may be considered fully referenced if one of the following criteria have been met
An item is complete as soon as it is used as a reference. In this case, the item is fully referenced, even if only a part of the quantity is copied.
An item is only complete once the full quantity has been copied into a subsequent document. If the item is partially referenced, it is possible to enter several sales documents for the item until the quantity is fully accounted for.
An item is only complete once the target quantity (in a contract, for example) has been copied into a subsequent document. If the item is partially referenced, it is possible to enter several sales documents for the item until the quantity is fully accounted for.
The standard version of the system defines an inquiry item as complete even if only one part of the inquiry quantity has been copied into a quotation. On the other hand, when you copy a quotation into a sales order, the quotation is not complete until the quotation quantity has been fully referenced.
Contracts, like quotations, are only considered complete once the full target quantity of the contract has been released.

Difference between Full Update V3 and V2

Hi Gurus
explain me briefly abt the difference between the full update V3 and V2..
pls post some links to understand in detail
regards
Prince

Hi Prince,
V1 Update: It is a Synchronous update. Here the Statistics update is carried out at the same time as the document update (in the application tables).
V2 Update: It is an Asynchronous update. Statistics update and the Document update take place as different tasks.
o V1 & V2 dont need scheduling.
Serialized V3 Update: The V3 collective update must be scheduled as a job (via LBWE). Here, document data is collected in the order it was created and transferred into the BW as a batch job. The transfer sequence may not be the same as the order in which the data was created in all scenarios. V3 update only processes the update data that is successfully processed with the V2 update.
FULL update, this will load everything which is there in the source system and then do INIT WITHOUT DATA TRANSFER to set the delta and schedule your delta loads accordingly.
Init Delta
You run an init delta from BW sytem using an info package .
Init delta will create an entry in R3 side table ROOSPRMSC with the filed init state with 'X' . Then upon this entry the system estbalishes a link between Extraction Queue . After succesfull initilization you can see the data source in RSA7 in R3 side . Then after this only you can extract data from the set up table .
Init Delta Types:
Init Delta
This will initialize the delta in R3 and exctract the set up table data into R3 . It is full update .
Init Delta without data transfer
This will only initialize the delta , No extraction takes place .
Use of init delta .
Without init delta you cannot schedule an Extraction . If you have initialized a delta , You can get delta reocrds from the succesive run in the delta Q .
When ever you need to do a extraction if for the first time you run a scheduler you will get
Full Update
Init Delta
Full Update =====> Init Delta + Extraction
Init Delta =======> Initialization first , Extarction
Init Delta Without data transfer ====> Only Initialize in RSA7 .
After the first Run u get ....Folowing in Scheduler
Full Update ,Delta Update .
Queued Delta: Document posting -->Appl table --> Stat table ---> 10,000 LUW ---> LBWQ ---> RSA7 ---> BW delta run delta into BW .
Here 10,000 Transaction is collected as 1 LUW and records moved to RSA7
In case of Queued delta LUW's are posted to Extractor Queue (LBWQ), by scheduling the V3 job we move the documents from Extractor queue to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. Generally we prefer Queued Delta as it maintain the Extractor Log which us to handle the LUW's which are missed.
Direct Delta:
Document postings -> Appl table -> Stat tables --> RSA7 (Delta Queue ) ---> Using delta run delta come into BW .
Here each transaction is 1 LUW and each LUW is moved to RSA7 .
In case of Direct Delta LUW's are directly posted to Delta Queue(i.e. RSA7) and we extract the LUW's from Delta Queue to BW side by running Delta Loads. If we use Direct Delta it degrades the OLTP system performance because when LUW's are directly posted to Delta Queue (RSA7) the application is kept waiting untill all the enhancement code is executed.
Non-serialized V3 Update:With this update mode, the extraction data for the application considered is written as before into the update tables with the help of a V3 update module. They are kept there as long as the data is selected through an updating collective run and are processed. However, in contrast to the current default settings (serialized V3 update), the data in the updating collective run are thereby read without regard to sequence from the update tables and are transferred to the BW delta queue.
https://websmp102.sap-ag.de/~sapdownload/011000358700007535452002E/HOWTOCREATEGENERICDELTA.PDF (need id)
http://help.sap.com/saphelp_bw33/helpdata/en/3f/548c9ec754ee4d90188a4f108e0121/frameset.htm
Business Intelligence Performance Tuning [original link is broken]
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/cccad390-0201-0010-5093-fd9ec8157802
How to load data
/people/sap.user72/blog/2004/12/16/logistic-cockpit-delta-mechanism--episode-one-v3-update-the-145serializer146
/people/sap.user72/blog/2004/12/23/logistic-cockpit-delta-mechanism--episode-two-v3-update-when-some-problems-can-occur
/people/sap.user72/blog/2005/01/19/logistic-cockpit-delta-mechanism--episode-three-the-new-update-methods
Delta Types and methods;&#57245;
Hope this helps.
****Assign Points if Helpful*****
Regards,
Ravikanth
Message was edited by:
Ravikanth.pnv

Give difference between full load, delta load, repair full load

Can i run full update after delta load?? if yes tell me a scenario??Can anyone tell me the difference between all three & when to use these??
Regards,
Asish

Hi,
For Repair full load please check OSS note 689964 which is about repairing the full load by executing the program RSSM_SET_REPAIR_FULL_FLAG.
Basically in this you provide your ODS, Data Source and Source System name and execute the program RSSM_SET_REPAIR_FULL_FLAG and hit Repair full load.
It will repair the full load.
But after this you cannot go directly for delta load which is for new added records or changed records. Before delta load do initialization without data loading and then go for delta load.
So delta load will run after init run (without data transfer) and add new added record or changed records to exisitng full upload records.
Technically you cannot go for delta load with out init load.
So, If you have already done full load, you can go for delta load after doing initializing (init load) without data loading.
Hope it helps.
Regards,
Mona

Difference between full version and academic version

So I just received my first FCE4 software but it has a sticker saying "Academic: Not eligible for upgrades"
I was wondering why the academic version was a little cheaper... I just wanted to know before I actually open this package, what kind of benefits would I be missing (other than not being able to upgrade to FCE5 I guess...) if I just decide to keep this academic version? Do you recommend just keeping this version or get a regular full version?

There are only 2 differences between the retail & academic versions, and they both pertain to the license, not the functionality of the software:
1 - the price of the academic version is lower than the retail version
2 - when you license (purchase) the academic version, you are not eligible to upgrade it in the future by purchasing an upgrade. (So, if you have FCE4 Academic Version, and someday FCE5 comes out, at that time you would have to purchase a full FCE5 Retail or FCE5 Academic in order to upgrade; you would not be eligible to purchase a reduced-price FCE5 Upgrade version.)

Differences between FULL, DELTA and REPEAT DELTAs

Please distinguish Full, Delta and Repeat Delta loading from R/3 to BW/BI and give some example for their uses
Your answer would be appreciated.
Cheers,
Nari

please search in SDN before posting Novice questions

Difference between Full settlement & periodic settlement

Similar Messages

Maybe you are looking for