What is Infopackage Group

Hi all,
What is Infopackage Groups and what are the settings in side
thanks in advance
regards

Hi Chaudhary,
Infopackage group is used to scheduled the group of infopackages. You can just put infopackages in the infopackage group and give the time gap between each package and start the job.
Info Package groups perform the same function as an infopackage only thing is you can attach more than one infopackage in a infopackage group and prioritise your load schedules infopackage wise.
In RSA1 click on Infosources . you'll see a icon for infopackage grooups on the middle panel beside the search,legend icon, click on it then a right panel opens where you can see the list of infopackage groups.Right click on the top node and say create.
Drag and drop your infopackagesfrom the left pane in it and right click and say schedule.
It will open a window enabling you to prioritise your info package loads in the order you wnt.
Hope this helps.
U can also check this link
http://help.sap.com/saphelp_nw04/helpdata/en/80/1a65b5e07211d2acb80000e829fbfe/frameset.htm
Amith.

Similar Messages

  • How to create infopackage groups & Process chains & what is the difference

    Hi gurus,
    please help me to create infopackage groups & Process chains & what is the difference.
    please explain any realtime scenerios.
    when will we choose infopackage groups & process chains
    and what is the difference betweeen these two.
    Thanks & Regards,
    BWcheta

    Cheta,
    You can create the IPG with the selction of all infopackages in RSA1-Modelling Area to automate those loads automatically. That means it will trigger only those IP's which have been pooled up in that IGP...
    Where as Process chain is also a automated process where you can have different process types which can be used during the load and after the load has been done.. For example in ODS once after the data has been loaded if you want to activate the data then in PC youo can insert the process type for that, but in case of IGP it will only execute your IP.
    Hope it helps...
    ******Assign Points*******
    Thanks,
    Gattu.

  • Step-by-Step procedure to create an InfoPackage Group & a Scenario!!

    Hello BW Experts,
    IF we have 10 InfoPackages and if we need to create an InfoPackage Group for 7 of them, How do we do it??
    Plz provide a detailed Step-by-Step procedure for the same/ create an InfoPackage group!!
    Ur help is really appreciated!!
    Thanks & Regards,
    Sapster.

    Hello Stefan,
    Thanks for ur response...with ur detailed steps..really helpful.
    While sheduling at the last ..by clicking the context menu of our created IP Group.. I am not getting any screen to schedule the same..(I am getting amessage at the mottom saying its not possible to run it in the back ground for my client workstation or similar to this)
    Could u plz let me know.. what it looks like for these remaining steps
    "Right click on the InfoPackage Group that you just created -> Schedule -> Check that all InfoPackages are selected -> Schedule the job just as you normally do with a InfoPackage."... thansk again.. assigend points...

  • Infopackage Group & Process chain

    Hi All,
    I read in documentation for Upgrade to BI 7.0, that infopackage groups needs to be migrated to Process chains, during upgrade.
    But I do find infopackage groups existing in RSA1OLD( after upgrade) and they can be scheduled and seems to function properly.
    1) So why is it necessary to convert infopackage groups to Process chain ?
    2) If I don't migrate to Process Chain, what problems could occur ( as client is more keen on keeping infopackage groups and not disturb the setup.)
    Regards,
    Sandeep

    Oops got posted twice....... Sorry

  • Use of four options in Processing tab at Infopackage group.?

    Hi Experts,
    Can any one give the details information about the Four options in Processing tab at Infopackage group.
    -PSA and then into data targets
    -PSA and data targets in parallel
    -Only PSA
    -Data targets only.
    Please give the info on what situations we can go for the above options, let me know what is the best option to go if the load is Master or Transaction data ?
    Points will be assigned . Please help me. as it is urgent
    thanks
    sekhar

    Processing options for the PSA transfer method
    In contrast to a data request with IDocs, a data request in the PSA also gives you various options for updating data in the BI system. Upon selection, you need to weigh data security against performance for the loading process.
    If you create an InfoPackage in the scheduler for BI, you specify the type of data update on the Processing tab page.
    The following processing options are available in the PSA transfer method:
    Processing Option
    Description
    More Information
    PSA and Data Targets/InfoObjects in Parallel (By Package)
    A process is started to write the data from this data package into the PSA for each data package. If the data is successfully updated in the PSA, a second parallel process is started. In this process, the transfer rules are used for the package data records, data is adopted by the communication structure, and it is finally written to the data targets. Posting of the data occurs in parallel by package.
    This method is used to update data into the PSA and the data targets with a high level of performance. BI receives the data from the source system, writes it to the PSA, and starts the update immediately, in parallel, in the corresponding data target.
      The maximum number of processes, which is set in the source system in Maintaining Control Parameters for Data Transfer, does not restrict the number of processes in BI. Therefore, many dialog processes in the BI system could be necessary for the loading process. Make sure that enough dialog processes are available in the BI system.
    If the data package contains incorrect data records, you have several options allowing you to continue working with the records in the request. You can specify how the system should react to incorrect data records. More information: Handling Data Records with Errors.
    You also have the option of correcting data in the PSA and updating it from here (refer to Checking and Changing Data).
    Note the following when using transfer and update routines:
    If you choose this processing option and then request processing takes place in parallel during loading, the global data is deleted because a new process is used for every data package in further processing.
    PSA and then to Data Target/InfoObject (by Package)
    A process that writes the package to the PSA table is started for each data package. When the data has been successfully updated to the PSA, the same process writes the data to the data targets. The data is posted in serial by package.
    Compared with the first processing option, you have better control over the whole data flow with a serial update of data in packages, because the BI system carries it out using only one process for each data package. Only a certain number of processes are necessary for each data request in the BI system. This number is defined in the settings made in the maintenance of the control parameters in customizing for extractors.
      If the data package contains incorrect data records, you have several options allowing you to continue working with the records in the request. More information: Handling Data Records with Errors.
    You also have the option of correcting data in the PSA and updating it from here (refer to Checking and Changing Data).
    Note the following when using transfer and update routines:
    If you choose this processing option and then request processing takes place in parallel during loading, the global data is deleted because a new process is used for every data package in further processing.
    Only PSA
    Using this method, data is written to the PSA and is not updated any further.
    You have the advantage of having data stored safely in BI and having the PSA, which is ideal as a persistent incoming data store for mass data as well. The setting for the maximum number of processes in the source system can also have a positive impact on the number of processes in BI.
    To further update the data automatically in the corresponding data target, wait until all the data packages have arrived and have been successfully updated in the PSA, and select Update in DataTarget from the Processing tab page when you schedule the InfoPackage in the Scheduler.
    A process that writes the package to the PSA table is started for each data package. If you then trigger further processing and the data is updated to the data targets, a process is started for the request that writes the data packages to the data targets one after the other. Posting of the data occurs in serial by request.
      When using the InfoPackage in a process chain, this setting is hidden in the scheduler. This is because the setting is represented by its own process type in process chain maintenance and is maintained there.
    Handling Duplicate Data Records (only possible with the processing type Only PSA):
    The system indicates when master data or text DataSources transfer potential duplicate data records for a key into the BI system. The Ignore Duplicate Data Records indicator is also set by default in this case. If multiple data records are transferred, the last data record of a request for a particular key is updated in BI by default. Any other data records in the request with the same key are ignored. If the Ignore Duplicate Data Records indicator is not set, duplicate data records will cause an error. The error message is displayed in the monitor.
    Note the following when using transfer and update routines:
    If you choose this processing option and request processing takes place serially during loading, the global data is kept as long as the process with which the data is processed is in existence.
    Further updating from the PSA
    Several options are available to update the data from the PSA into the data targets.
    ●      To immediately update the request data in the background, select the request in the PSA tree and choose Context Menu (Right Mouse Button) ® Start Update Immediately.
    ●      To schedule a request update using the Scheduler, select the request in the PSA tree and choose Context Menu (Right Mouse Button) ® Schedule Update.
    The Scheduler (PSA Subsequent Update) appears. Here you can define the scheduling options for background processing. For data with flexible update, you can also specify and select update parameters where data needs to be updated.
    ●      To further update the data automatically in the corresponding data target, wait until all the data packages have arrived and have been successfully updated in the PSA, and select Update in DataTarget from the Processing tab page when you schedule the InfoPackage in the Scheduler.
    When using the InfoPackage in a process chain, this setting is hidden in the scheduler. This is because the setting is represented by its own process type in process chain maintenance and is maintained there.
    Simulating/canceling update from PSA
    To simulate the data update for a request using the Monitor, select the request in the PSA tree, and choose Context menu (right mouse button) ® Simulate/Cancel update.
    The monitor detail screen appears. On the Detail tab page, select one or more data packages and choose Simulate Update. In the following screen, define the simulation selections and select Execute Simulation. Enter the data records for which you want to simulate the update and choose Continue. You see the data in the communication structure format. In the case of data with flexible updating, you can change to the view for data target data records. In the data target screen you can display the records belonging to the communication structure for selected records in a second window. If you have activated debugging, the ABAP Debugger appears and you can execute the error analysis there.
    More information: Update Simulation in the Extraction Monitor
    Processing several PSA requests at once
    To process several PSA requests at once, select the PSA in the PSA tree and choose Context Menu (Right Mouse Button) ® Process Several Requests. You have the option of starting the update for the selected requests immediately or using the scheduler to schedule them. The individual requests are scheduled one after the other in the scheduler. You can delete the selected requests collectively using this function. You can also call detailed information, the monitor, or the content display for the corresponding data target.

  • Infopackage Group to Process Chain Conversion

    Dear Gurus,
    We are going to do BI upgradation,prrequisite for that we have to convert all Infopackage groups in to Process Chain.In our system totally we 600 Infopackage groups.Let me know the optimized and oraganized way to make a process chain conversion.Before the conversion process, what are the basic measurement (Like sequence,Grouping under process chain,Scheduling .Etc...) I have to do.Anticipate your respone eagerly.
    With regards
    Siva

    Hello Sivakumar,
    Try this Function Module RSPC_MIGRATE_INFOPACKAGE_GROUP , this should help you.
    You can also goto Process Chain Maintanance in the InfoPackage Group and create the Process Chain.
    If that doesn't then as a manual process, you have to note down all the InfoPackage sequence and include them in the Process Chain in the same order.
    Thanks
    Chandran

  • InfoPackage groups

    hi all,
    Please any one tell me about infopackage groups and where is the option to create it. What is the difference between infopackage groups and process chain?
    Thanks in advance,
    Manoranjan

    Hi Manu,
      Infopackage groups are used to use to do Data Transfer before Process Chain concept introduced which is before 3.0b version of BW. Since process chains has more features and functionalities than Infopackage groups now every one is using process chain concept.
        Infopackage groups are used to use to do Data Transfer before Process Chain concept introduced which is before 3.0b version of BW. Since process chains has more features and functionalities than Infopackage groups now every one is using process chain concept.
        Info Package groups perform the same function as an infopackage only thing is you can attach more than one infopackage in a infopackage group and prioritise your load schedules infopackage wise.
    In RSA1 click on Infosources . you'll see a icon for infopackage grooups on the middle panel beside the search,legend icon, click on it then a right panel opens where you can see the list of infopackage groups.Right click on the top node and say create.
    Drag and drop your infopackagesfrom the left pane in it and right click and say schedule.
    It will open a window enabling you to prioritise your info package loads in the order you wnt.
    regards
    @jay

  • I want to know Cube,Ods,Multiproviders,infopackage groups,process chains

    Hi all,
    1.how to make techinical specifications Cube,Ods,Multiproviders,infopackage groups,process chains.
    2.how to decide the size of the cube.
    3.what is the default size& what is the max size & In the case of ods.
    4.performance wise which is best multiprovider or cube.
    5.why cube is best (performance wise) for  cube over ods.
    6.What is max no of chars & keyfigures can insert in ods.
    7.Is sid concept exists for ods.if yes when they generate.
    Thanks
    cheta.

    Hi
    1.From functional specification requirements,find out the datasources by using business content check(offline) or using Metadata repository(online), u need to have TREX installed in ur system.Do the GAP Analysis and note down the objects which are not in business content and create Z objects(Datasources,ODS or Infobjects,Cubes). Draw the bubble diagram and derrive ER diagram from it and finally do logical information model(cube model) and decide what u need in data flow.
    2.You have a quick sizer in market place which can help you to decide the sizing of BI project.Take care of trade-off's between line item dimensions and normal dimension which have large impact on ur sizing.
    3.There is no such default sizing,depends on ur reporting requirements whether u need detailed reporting or snap shot reporting.
    4.There is no trade-off's between multiprovider and Cube regarding performance.From performance point of view we have to consider other factors such as aggregates,Indexing,Partitioning etc..
    6.The Max number of Keyfields are 16 and data fields are 749.
    7.Yes SID's are created for ODS when you check the flag for BEX Reporting.
    Thanks
    Chandru

  • Infopackage Group settings

    Hi,
    Still we are using Infopackage groups..!!! instead of PC.
    We are facing one typical problem ,even though we have kept Infopackages in sequence and also checked the option "Check whether previous request was updated error free ,Then start next request" still next request is getting started before finishing the earlier request.
    Due to this masterdata is facing some locking issues which is causing errors.
    Has any one faced this kind of problem,please advise what could be the root cause.
    Thanks in advance,
    BRB

    Hi,
    Try it out and update me the status. I have worked on Event chains and Infopackage groups. I can give you an alternate solution if it doesn't work.
    You have mentioned:
    In the Infopackage group, Infopackages in sequence and also checked the option "Check whether previous request was updated error free ,Then start next request" still next request is getting started before finishing the earlier request.
    Due to this masterdata is facing some locking issues which is causing errors.
    *I hope you are comfortable at events.
    In an infopackage group, an infopackage may have any of the following start events.
    a. Immediate
    b. Date/time (time dependent)
    c. After Event
    4. After Job
    In your case, request 2 is starting before finishing request 1. You might be facing the locking issues because, they are accesing the same table.
    Better you define the events for the both requests in order to trigger them in sequence.
    Start event of Request 2 should be the subsequent event of Request 1. Then request 2 will wait for successful completion of request 1.
    If you are still facing the problem, send me the below details. I will look into it.
    i. Start event of the Infopackage group and the status whether it is scheduled in background.
    ii. Start and subsequent events of both the requests and the status whether they are scheduled in background.
    Regards,
    Sashi

  • How to Convert INFOPACKAGE GROUPS to PROCESS CHAINS???

    Hi BW Gurus,
    How to Convert INFOPACKAGE GROUPS to PROCESS CHAINS???and what are the
    measures i need to take care before doing the same .
    prasad

    Hi,
    Simply add these infopackage groups into process chain and schedule the process chain.
    Hope this helps.
    Assign points if useful.
    Regards,
    Venkat

  • Differences Between Infopackage Groups and Process chains

    Hi All,
    Can anybody explain me what are the differences between Infopackage Groups and Process Chains ? And how process chains are more comfortable

    hi nagarjuna,
    An InfoPackage group is a collection of InfoPackages. In order to summarize data requests which logically belong together from a business point of view, and to therefore simplify the request, you can collect data requests (meaning the InfoPackages) into an InfoPackage Group. You can schedule each of these groups in the scheduler . With the data request the scheduler can access InfoPackage groups directly and thereby request more than one InfoPackage at a time, corresponding to the setting in the InfoPackage group. Thus, you can support InfoPackage groups with the serialization of your data requests.
    While a process chain is a sequence of processes that wait in the background for an event. Some of these processes trigger a separate event that can start other processes in turn. hit this link to know abt PCs:
    http://help.sap.com/saphelp_nw04/helpdata/en/8f/c08b3baaa59649e10000000a11402f/content.htm
    Process chains are more comfortable becoz itz not like infopackages where we have to schedule each pack individually. And in PCs, monitoring is very convenient since u see evrything in a single page.
    regards
    sham'm

  • InfoPackage Group reschedule ...!

    We have the nightly loads set up to run under username SAPBatch. When a load fails, we either have to rerun each of the InfoPackages individually (a painful tedious process) or cancel the SAPBatch job so we can reschedule the InfoPackage Group (which means the Basis Team has
    to reschedule it under SAPBatch).  An obvious third alternative is to create duplicate InfoPackage Groups for use when we need to rerun a job (but that means duplicate maintenance and I can't find any easy way to (create a copy).
    My questions:
    1. Why do we do it that way?  What are the benefits of running under SAPBatch?  What are the disadvantages of running under a real user's name?
    2. Is there another alternative?  Some way of rerunning the InfoPackage Group without stopping the SAPBatch job?  Or some other way of getting the job done?
    3. Is there any way other than building one from scratch (which takes forever)?
    4. What do other BW users do?  Is there anything that is considered a "best practice"?

    1. Why do we do it that way? What are the benefits of running under SAPBatch? What are the disadvantages of running under a real user's name?
    <i>It is good to use a common Batch ID which has maximum auth coz,
    1> No need to worry abt individual user auth who will run that job
    2> Users might change frequently, so jobs scheduled under their name will suffer if their ids are removed.</i>
    2. Is there another alternative? Some way of rerunning the InfoPackage Group without stopping the SAPBatch job? Or some other way of getting the job done?
    <i>If you have your jobs are scheduled based on events, it is very easy just to trigger that event to start the job.</i>
    3. Is there any way other than building one from scratch (which takes forever)?
    <i>Instead consider swithcing all stuff to Process Chains. INfopPack groups are no longer supported by SAP I guess.</i>
    4. What do other BW users do? Is there anything that is considered a "best practice"?
    <i>Process Chains!</i>
    Regards,
    Sree

  • InfoPackage Group Terminates

    Hello Experts,
    We are experiencing a problem in our production environment.  A couple of our Infopackage groups are randomly terminating.  The message we receive is "Checking and waiting for request REQU_.... has been terminated. - Error 1 - Row 504".  The terminations are not consistently on a daily basis nor does the termination occur at the same infopackage within the group.  It is random in nature and difficult to reproduce.  We are currently running BW 3.1 with SP22 (SAPKW31022).  The problem sounds a lot like what is described in note 616014 except the BW version doesn't match up.  Any assistance you can give is greatly appreciated!
    Best Regards,
    Teri

    Hi
    The InfoPackage Group contained two InfoPackages pointing to the same data target. Due to STAT's switched ON, on the Data Target, it was causing ALEREMOTE locked.
    The other infopackage was executing after the first one was done, but at the InfoPackage Level there is no control on the STAT job.
    hence, I have removed the STAT execution after each data load from the data target.
    Regards,
    Praveen.

  • Abt infopackage group

    Hi All,
    How to check ,in infopackage group,how to check the individual info packages for which the background batch job exists.

    Hi,
    infopackage group holds group of info packages with
    proper sequence of execution.
    Infopackagegroup will have one background job means all the infopackages in the infopackage group completes,then job will be finished until job shows active only.
    If  infopackge group is opened, we can observe a push button which is related to background job. if we click push button, we can observe the job info then choose the job , click on  job detais , the job log may provide how many requests completed and what request is currently running.
    This may help for analysing your problem.
    Regards,
    Chendrasekhar

  • Functionality of Infopackage groups in BI 7.0

    Does anyone know how to use Info package groups functionality in BI 7.0?

    An InfoPackage group is a collection of InfoPackages.
    InfoPackage groups are replaced by process chains:
    Description
    InfoPackage groups are replaced by process chains.
    More information: [Process Chain|http://help.sap.com/saphelp_nw70/helpdata/en/8f/c08b3baaa59649e10000000a11402f/frameset.htm]
    General Practices with Migration
    You call the InfoPackage group tree in transaction RSA1OLD. From there, you select the InfoPackage group. In the maintenance for the InfoPackage group, you select Process Chains. The InfoPackages of the InfoPackage group are then embedded in a process chain.
    InfoPackage Group -> Process Chain
    http://help.sap.com/saphelp_nw70/helpdata/en/43/fc5cb587e1025de10000000a1553f7/frameset.htm
    InfoPackage Group
    http://help.sap.com/saphelp_nw04s/helpdata/en/80/1a65b5e07211d2acb80000e829fbfe/frameset.htm
    Regards
    Andreas
    Edited by: Andreas Schindler on Jun 12, 2009 12:45 PM

Maybe you are looking for