Difference between Bucket capacity and Time continuous capacity

Can somebody explain the difference in functionality between "Bucket capacity" and "Time continuous capacity" as used in field "Finite capacity" in "PP/DS bucket capacity"  tab in Resource?
How will above above two settings work when you have "Block planning" in  "Bucket definition" tab in same tab?
Thanks,
Srini

Hello,
The difference between Bucket capacity and Time continuous capacity are:
Time continuous capacity is basically the capacity which is infinite continuous duration in time and you can define the shift intervals and breaks to adjust as per business process e.g. everyday 8 hrs or 16 hrs capacity with lunch time and breaks in between whereas bucket capacity is a discrete capacity and is specified bucket wise. Bucket capacity can be in PPDS as well as SNP. In PPDS it is used specifically for CDP planning or block planning. In SNP it can be used for bucket capacity references as Transport resources, storage resources , bucket planning etc
With respect to Block Planning:
You maintain the blocks using the entire validity of the available capacity of the resource. If you defined buckets from block planning for validity periods in which no blocks are defined, the buckets correspond to technical intervals in which the system schedules on a time-continuous basis.
You  can check out the below link for the Block planning with Bucket capacity:
http://help.sap.com/saphelp_scm41/helpdata/en/e5/90bb3b6070bf38e10000000a11402f/content.htm
Hope the information is useful
Regards

Similar Messages

  • Difference between two dates and time in hours

    Hi,
    I have fields contains start date, start time, end date, end time.
    How do I calculate the number of hours since start date, start time and end date, end time
    Start date : T_DATE1
    Start time : T_TIME1
    End Date : T_DATE2
    End Time : T_TIME2.
    Please help
    Moderator Message: Date and Time questions are not allowed in this forum. The reason being they have been asked and answered many times here. Please search for relevant information here.
    Edited by: kishan P on Dec 16, 2011 12:02 PM

    Hi,
    Please find the FM - DELTA_TIME_DAY_HOUR,
    this will give you the time in minutes, hence you can convert it to hours.
    Please note the below links;
    Moderator Message: Link-farm removed. Please dont do that again.
    Hope you will search SDN next time, before posting.
    And too hope that this will help you
    Thanks & Regards
    Manu S
    Edited by: kishan P on Dec 16, 2011 12:03 PM

  • Difference between DB CPU and DB Time

    Hi,
    What is the difference between DB CPU and DB TIME in AWR report?
    Br,
    Raj

    Hi,
    Thanks for your valuable reply.
    1,DB CPU is time spent on CPU. It means only ACTIVELY working on CPU. WAIT TIME is not includeed.
    In 10 Minute interval with four CPU, Is the Maximum DB CPU 40 Minutes?
    2,I read the below document about DB time. http://www.perfvision.com/docs/JB_AAS.pdf
    I unable to understand at page 6.
    It says that DB Time = Includes CPU Time + IO Time +  Wait Time
    I understand about Wait time.
    CPU also involved  to do I/O Time? Is it RIGHT?.Hence, Why did seperate CPU Time and I/O time in the document?What is the purpose of it?
    Is it possbile to further divided the CPU TIME ? Like parse etc.....Which view provide it?
    3,If you had four sessions actively working or actively waiting 100% of the time in that 10 minute period, then your DB time would be 40 minutes.
    In a given interval,Where can i find NON Idle wait time in AWR?
    Plese help me out it
    Br,
    Raj

  • DIFFERENCES between BASIC SCHEDULING and LEAD-TIME SCHEDULING.

    Hello SAP Gurus,
    Kindly let me know the differences between BASIC SCHEDULING and LEAD-TIME SCHEDULING.
    Looking for your early feedback.
    Warm regards,
    Kaushik.

    Hi,
    Basic scheduling :
    1.Basic dates are calculated.
    2.Exact to day.
    3.No cap reqmts are generated.
    4.uses the inhouse production time from material master.
    5.carried out automatically during planning run.
    In basic date calculation ( order start date/ order finish date ) the system always
    calculates backward scheduling.
    1. From the reqmts date the system subtracts the GR processing time to
    calculate the order fininsh date.
    2. From the order finish date the system subtracts the inhouse production time to calculate the order start date.
    3. From the order start date the system subtracts the opening period given in scheduling margin key to calculate the order opening date.
    Lead time scheduling :
    1.Exact to second
    2.ie production start date /time and finish date and time are calculated.
    3. cap reqmts are generated.
    4. uses times from routing.
    5. carried out only if the scheduling mode in MD02 screen is kept with indicator 2.
    From the order finish date the system subtracts the float after production to calculate the production finish date.
    From the production finish date the individual operations in the routing are scheduled backwards to calculate production start date.
    From the production start date the system subtracts the float before production
    to calculate order start date.
    Regards,
    nandha

  • Difference between SNP PDS and PPDS PDS

    HI Experts.
    Can you tell the major differences between SNP PDS and PPDS PDS.
    Thanks
    Raja kiran R

    Hi Raja,
    Unlike PPDS planning (time-continuous planning), the least time bucket in SNP planning (bucket oriented planning) is a day, not seconds. Which is why the duration of individual activities in SNP PDS are planned in days only. Scheduling in SNP is based on the fixed duration of an activity and not based on order quantity or capacity load. If a plan contains 3 activities each with fixed duration of 1 day, then the SNP planned order will have duration of 3 days.
    On the other hand in PPDS, the duration of an acitivity is calculated based on the resource load that generates the order quanitity, which means larger the qty to be produced, the longer the duration of the activity.
    Hope this helps!
    Regards,
    Umesh

  • Difference between parallel sequence and parallel operation in a routing.

    Hi Experts,
    Can any one explain me with example the difference between parallel sequence and parallel operation in a routing? wHEN CAN WE USE PARALLEL OPEARTION AND PARALLEL SEQUNCE WITH COMPONENT ALLOCATION.
    Regards
    Deepak sharma

    I think u need to modify ur quest... i think u r asking about Parallel sequence and alternate seq. Below are the details from SAP site.
    A parallel sequence enables you to process several operations at the same time.
    You use an alternative sequence for example, if
    --The production flow is different for certain lot-size ranges
    For instance you can machine a work piece on conventional machine or on NC machines. A NC machine has a longer set-up time than a conventional machine. However the machining costs are considerably less. Therefore whether you use NC machines will depend on the lot size.
    ---The production flow changes under certain business conditions.
    For instance, if you have a capacity problem, you have some production steps performed externally by a vendor.

  • Difference between Master Idoc and Communication Idoc.

    Can anyone list out the difference between Master Idoc and Communication Idoc?

    IDoc (for intermediate document) is a standard data structure for electronic data interchange (EDI) between application programs written for the popular SAP business system or between an SAP application and an external program. IDocs serve as the vehicle for data transfer in SAP's Application Link Enabling (ALE) system. IDocs are used for asynchronous transactions: each IDoc generated exists as a self-contained text file that can then be transmitted to the requesting workstation without connecting to the central database. Another SAP mechanism, the Business Application Programming Interface (BAPI) is used for synchronous transactions.
    Form and content: IDoc terminology
    As is often the case with proprietary technologies, SAP assigns specific, object-oriented meanings to familiar terms. When referring to IDocs, the term document refers to a set of data comprising a functional group of records with a business identity. (For example, all the data in a purchase order, or all the profile information of a supplier in a supplier master record.)
    A message refers to the contents of a specific implementation of an IDoc; it’s a logical reference. This differs from a reference to the IDoc itself, which specifies the message’s physical representation. Think of it this way: If you’re watching a parade pass by, the mayor waving to the crowd from his limousine is the message, and the mayor’s limousine (which is specific to the mayor) is the IDoc. You’re building a logical object, and the IDoc is both its container and the vehicle that moves it.
    The IDoc control record
    Each IDoc has a single control record, always the first record in the set. The structure of this record describes the content of the data records that will follow and provides administrative information, such as the IDoc’s functional category (Message Type/IDoc Type), as well as its origin (Sender) and destination (Receiver) as in conventional EDI
    Layout of an IDoc control record
    This “cover slip” format informs the receiving system of the IDoc’s purpose, and the receiving system uses it to determine the correct processing algorithm for handling the arriving IDoc.
    Data records
    The data records following the control record are structured alike, including two sections: a segment information section and a data section.
    In the first part of a data record, the segment information section describes the structure of the data that follows, for the benefit of the IDoc processor. There is a segment name (like an EDI segment identifier) that corresponds to a data dictionary structure to which the IDoc processor has access. The remaining information is useful for foreign systems, such as a partner company’s Oracle system, which has no such data dictionary.
    The second part of the record is the data itself, a storage area of 1,000 characters.
    Status records
    If you’ve ever ordered a package from a faraway location and tracked its progress using the Internet-based tracking utilities now provided by most major parcel carriers, you’re familiar with the list of stops and transfer points through which a package passes on its way to you.
    This collection of records is exactly what you’ll see in an IDoc that has begun its work. Following the data records in an IDoc, status records accumulate as an IDoc makes its way from one point in a process to another.
    Typically, an IDoc will acquire several of these records as its does its job. They are simple records, consisting of a status code (there are more than 70 codes, covering a broad range of conditions and errors), a date/time stamp, and some additional status information fields for system audit purposes. In addition, as errors occur in the processing of an IDoc, status records are used to record these errors and the date/time of their occurrence.
    IDoc Base
    IDocs, as data formatting tools, enable the easy sharing of data between databases and applications within a company as well as being an efficient data courier between companies. Typically in SAP, a database of IDoc definitions exists, to which any application may have access.
    This “IDoc Base” gives all the applications and processes in your company domain the capacity to send, receive, and process a document in a contextually appropriate way, without doing anything to the data. For example, a purchase order IDoc can filter through every process it touches, passing from system to system, accumulating status records to track its progress.
    Every department using the data can use it appropriately without any cumbersome intermediate processes, because each department draws its key to interpreting the IDoc from the same source.
    Multiple messages
    One cumbersome feature of conventional EDI is the embedding of more than one functional record type in a document. The unwieldy X-12 888 Item Maintenance transaction set is an example: It purports to handle so many different configurations of product master data that it is horrifically difficult to integrate into an existing system.
    IDocs, on the other hand, handle multiple messages with ease. Given the centralized IDoc interpretation that SAP provides to all its parts, it’s no problem to define an IDoc that will contain more than one message, that is, more than one data record type.
    A customer master IDoc, for example, may contain customer profile information records for a customer with many locations. But it may also contain location-specific pricing information records for that customer in the same document. This is an incredibly efficient way of bundling related records, particularly when passing large amounts of complex information from system to system Records in a multiple-message IDoc

  • Difference between Ace Director and Ace Memeber

    What is the Difference between Ace Director and Ace Member?
    because recently I saw one Ace director becoming Ace Member... (John)

    You have not read the link I provided, have you ?
    Ace director are not more senior than Ace member, they have more things to commit to like "Ability to commit to participation in an honorary (noncompensated) capacity for 12 months"...
    So, I cannot tell for John, but if one cannot commit within those things, you cannot be Ace director... and it is not "depromoted", probably have less time for this.
    Nicolas.

  • What is difference between bex analyser and bex browser

    what is difference between bex analyser and bex browser . please explain what are use of both and what we do in both.

    hi
    Bex Browser
    The Business Explorer Browser (BEx Browser) makes it possible for you to access all document types of the Business Information Warehouse that are assigned to your role or that you have stored in your favorites. You can select and open documents assigned to you in the BEx Browser or store and manage new documents in the BEx Browser.
    Document types that you can work with in the BEx Browser are:
    · BW workbooks
    · Documents that are stored in the Business Document Service (BDS)
    · Links (references to file system, shortcuts)
    · Links to internet sites (URLs)
    · SAP transaction calls.
    · Web applications and Web templates
    · Crystal Reports
    Bex Analyser
    The Business Explorer Analyzer (BEx Analyzer) is the analysis and reporting tool of the Business Explorer that is embedded in Microsoft Excel.
    Features
    You can call up the BEx Query Designer in the BEx Analyzer, in order to define queries. Subsequently, you can analyze the selected InfoProvider data by navigation to the query created in the Query Designer and create different query views of the data. You can add the different query views for a query or for different queries to a work book and save them there. You can save the workbook in your favorites or in your role on the BW Server. You can also save the workbook locally on your computer.
    Beyond that, you can precalculate the workbook and distribute it by e-mail to recipeients or you can export it to the Enterprise Portal and make it accessible to other employees in the company.
    You can start queries in a standard view (with a Standard Web Template set up in Customizing) in the Web browser and forward the URL or continue to navigate on the Web. Similarly, you can export the Web query to MS Excel 2000.
    Overview of the Functional Area of the BEx Analyzer:
    ·        BEx toolbar
    You access the functions of the BEx Analyzer from the BEx toolbar, which takes you to the BEx Open dialog box where you can open existing queries, or to the BEx Query Designer where you can create new queries or change existing queries.
    ·        Evaluating Query Data
    The BEx Analyzer offers convenient functions for evaluating and presenting InfoProvider data interactively. In the BEx Analyzer, you can add queries to workbooks, navigate within them and refresh the data. You can also process the queries further in Microsoft Excel or display them in the Web browser in a default view.
    Navigation of a query allows you, for example, to filter characteristics on a single value, drilldown on all values for a characteristic, regroup characteristics and key figures in the rows and columns of the results area, or hide key figures. Navigation results in different views of the InfoProvider data. In addition, a range of further functions is available which allow you to edit a query interactively (for example, sorting, cumulated output, among others). In addition, you can use the editing functions in Microsoft Excel in order to set up individual format templates, to print results areas, or to create graphics.
    ·        Queries in Workbooks
    Queries are inserted into workbooks so you can display them. When you insert a query, a link is made between the cell areas of the worksheet and the data of the InfoProvider upon which the query is based. A link therefore exists between the Business Explorer and the Business Information Warehouse Server (BW Server).
    When inserting a query into the workbook, a VBA routine is automatically generated in the workbook. You can also connect the Business Explorer with your own VBA programs (Visual Basic for Applications).
    You can create workbook templates, into which you can insert your queries. Workbook templates can contain pre-determined items for the area of the query, formatting settings, logos, VBA macros, and so on.
    ·        Precalculating workbooks
    You can precalculate and distribute workbooks with the BEx Broadcaster, which is a Web application you get to form the BEx toolbar. The system generates MS Excel workbooks with historical data. You determine the time for precalculation yourself: You can have workbooks precalculated at a predefined time or they can be precalculated whenever data in the underlying InfoProvider changes. You can have the precalculated workbooks sent by e-mail or you can export them into the Enterprise Portal, where you can make them available to employees within your company.
    Activities
    To start the BEx Analyzer, choose Start ® Programs ® SAP Front-end Business Information Warehouse ® SAP Business Explorer Analyzer.
    You can also access the BEx Analyzer via SAP Easy Access ® SAP Business Information Warehouse ® SAP Menu ® Business Explorer ® Analyzer or in the Business Explorer Browser using the Business Explorer Analyzer symbol in the menu bar.
    Hope this will solve your issu
    nagarjuna

  • What is difference between SAP R3 And SAP IS Mills Product

    HI Friends
    What is difference between SAP R3 And SAP IS Mills Product
    What are the futures are availables in IS MIlls
    Regards

    Hi,
    SAP R/3 is the central enterprise version. It is not specifically designed for any inducstry sectors and it can cater many of the industry types.
    Is is developed for specific industries an for SMB's (small and medium business). It will have components specifically for the industry.
    The SAP Mill Products component adds sector-specific functionality to an ERP system to satisfy the complex requirements of mill industries (e.g. metal, wood, paper, textiles, construction materials, and cable sectors).
    These industry segments differ from others primarily in that the materials used have a large number of characteristics and variants. The materials in the segments listed above are also predominantly area-based (e.g. paper, textiles, plastic film) or length-based (e.g. cables, piping). Account must be taken of these material characteristics throughout the entire supply chain.
    To cater for the particularities of these industry segments, SAP Mill Products features processes and functions that cover the entire supply-chain cycle – from product design and configuration, through planning, order processing, capacity planning and production, to final delivery. Additional functions are available in costing and inventory management. SAP Mill Products are also integrated into Quality Management, Financial Accounting, and Controlling.
    Prase

  • Any basic differences between AT&T and Verizon, & other questions

    I am thinking of buying an iPad mini with retina display (32gb). This would most likely be the only iPad I would ever own. I would use it mostly at the house with wifi, but would like to have one with cellular for when we travel in the US and Canada, and for when the electricity goes out. We currently live in a location where both AT&T and Verizon are viable options, but sometime in the next year we hope to move. The state is rural and mountainous, so as we drive around, my spouse's iPhone (with an AT&T plan) often loses service, but so does my Jitterbug phone, which is not tied to any one carrier (as far as I know). A phone can get a signal in one locaton, but then lose it a few feet down the road. So, there is no way I can choose between AT&T or Verizon based on coverage because both are options right now and there is no way to predict which one(s), if any, might provide service to wherever we end up moving to. Therefore, I'm wondering if there are any basic differences between AT&T and Verizon (or any other of the possible carriers) in what they offer or how they work or what they charge and so on that can help me decide which one to choose since it is my understanding that once I pick one of them for an iPad, that decision can never be changed without purchasing a new device. (e.g., I had read somewhere that Verizon does not allow for voice and data at the same time, but since an iPad is not a phone, is that even an issue?) Also, will the iPad work if there is only regular 4G or 3G service? And will a cellular iPad work without signing up for a data plan since I expect to start with only wifi and then add a data plan later? Thank you.

    Alfred DeRose, Thank you for answering the second and third questions. Judging by what you wrote, I am assuming there are no differences between what AT&T and Verizon offer that affects iPads, other than looking at coverage area and the cost of "pay as you go" plans. And, as noted, coverage is not something I can base a decision on at this time. So, I either flip a coin to choose between AT&T and Verizon and hope the result is the right one after we move to wherever we end up finding a place to live, or I continue to wait for another year or more until we actually find a new house before I buy an iPad (or maybe a Kindle Fire HDX 8.9"to save money, but I think I've probably settled on an iPad mini retina 7.9" despite its smaller screen). That does not move me along the decision-making process at all, but it is what it is.
    Greatcall has not answered my question about what carrier(s) the Jitterbug Plus phone uses. If, in fact, it uses just the Verizon network, I will try to pay better attention to any possible differences in service areas between that phone and my spouse's iPhone as we travel around the state to see if that helps at all. But coverage is so location specific here that I don't think it will.

  • Difference between business blueprint and functional spec

    hello
    can somebody please tell me the difference between business blueprint and functional spec and how they are interrelated
    Thanks

    Hi Comandante,
    Business Blue print is a detailed documentation of the requirements gathered from client (The objects we need to develop are modified depending upon clients requirements).It represents the business process requirements of the company.  It is an agreed statement of how the company intends to run its business within SAP system.
    Functional specifications (functional specs), in the end, are the blueprint for how you want a particular report and transaction to look and work. It details what the report will do, how a user will interact with it, and what it will look like. By creating a blueprint of the report or transaction first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect. Functional Spec streamlines the development process.
    A functional specification  is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. It guidelines and continuing reference point as the developers write the programming code.
    Other processes include Requirements, Objectives,Logic Specification,User documentation,The Final Product.
    Hope this Helps, Revert for any further info.
    Cheers,
    Tanish

  • Difference between Conversion progs and INTERFACES

    Hi  plz     tell me  ...
    whats  the difference between    Conversion progs and Interfaces in ABAP .
    wat are  conversion progs  ( exmple) and interfaces  ( exmple ) ?
    thnks in advance....

    Hi
    CONVERSION programs are the ones which have one time usage, usually when a legacy system is being replaced by a system like SAP, then the data has to be mapped from the legacy system to SAP system. Here the data to be converted is given on a flat file & is uploaded to SAP tables mostly using LSMW only. Conversions programs are BDC,BAPI and LSMW programs in which you upload all the related tables from the flat files.Those are one time programs.
    Interface programs are those programs in which you fetch the data from the application server and process on theose data.These are helpful when you have to run any program in the backgroup when the presentation server is not working.
    INTERFACE programs are the ones which are run at regular intervals, say weekly, monthly or even daily. Here the legacy system continues to co-exist along with SAP system, the legacy system might be useful for certain functionalities but the data might have to run thru SAP transactions for complex data maintenance at regular intervals.
    In Simple
    CONVERSIONS : Converting Legacy System DATA into a flat file
    INTERFACES : Converting Flat File into SAP
    Conversion Program
    http://help.sap.com/saphelp_erp2005/helpdata/en/d3/a65a14e96911d1b401006094b944c8/frameset.htm
    Interface Program
    http://help.sap.com/saphelp_erp2005/helpdata/en/64/be5b4150b38147e10000000a1550b0/frameset.htm
    <b>Reward if usefull</b>

  • What's the difference between the ssd and hd?

    I'm in the process of buying a Mac book pro but wanted to know and understand What's the difference between the ssd and hd?

    DDHeadley wrote:
    What's the difference between the ssd and hd?
    HD = hard drive, several metal platters stacked and data read/written magnetically.
    Pro's - less expensive and higher capacity of storage. Can scrub the drive of unwanted data. Unlimited write capability.
    Con'- bit rot can cause data and operating system to not be as reliable, mechanical moving parts means you can't move the machine while it's on.
    SSD = Solid State Disk, basically memory chips that can store data in a permanent fashion without power (like Random Access Memory needs)
    Pro's - faster read/write speeds in most cases. Shock resistant makes them ideal for portable uses.
    Con's - new technology issues, one cannot securely erase the data on them, unless it's ground into a fine powder. Limited write capability means they will wear out eventually like USB thumb drives do. Wear leveling (TRIM) is used to spread the writes evenly across the drive to maximize it's lifespan.
    If you can respect the machine, take care of it and not move it while it's on, or need to scrub the drive of unwanted data, or need higher capacity of storage without paying a fortune for a very large SSD, then a HD makes a lot of sense.
    It really comes down to your privacy, do you want a machine you cannot delete files off of?
    Do you want to carry around a machine that has all your dirty secrets etched in it for anyone with the right software to uncover?
    A computer is a personal machine, why it's called a Personal Computer. We all do things we sometimes are later ashamed of and want to erase all memory of it.
    Can't do that with a SSD, it knows all and you will be forced to destroy the machine to rid it of the unwanted data.

  • 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

Maybe you are looking for