InfoPackage Processing Type

Sometimes when I'm in an InfoPackage under the Processing tab I see either:
ALE Inbox and InfoObject (i.e. 0sales_grp)
PSA and then the InfoObject (i.e. 0sales_off)
Why the inconsistency of processing? Do I care?

Hello Michael,
"ALE" means that data records and status information are transmitted via IDocs. "PSA" in this context means that status records are transmitted via IDocs and data records via RFC LUWs.
"PSA" offers the opportunity to use the PSA as a intermediate storage layer. This cannot be done by using ALE. Furthermore I guess that PSA is faster than ALE.
It depends on the DataSource which processing method can be used. More information can be found here: http://help.sap.com/saphelp_nw70/helpdata/en/b8/5b723b9b4f8f7de10000000a114084/frameset.htm
Kind regards,
Stefan

Similar Messages

Process type "Delete overlapping request in cube " in process chain

Hi
can somebody suggest me where i need to place the process type "Delete overlapping request" for an infocube.
Regards,

Hi,
When you use the corresponding process in the process
chain maintenance screens to specify the conditions for
automatic deletion, these conditions are applied to all
the InfoCubes for the selected InfoPackages
Overlapping: If you set this indicator, existing requests are also
delete from the InfoCube if the selection criteria of the new request partially or wholly overlap the selection criteria of the request to be deleted
Same or Comprehensive: If you set this indicator,
requests are only deleted from the InfoCube if
the selection conditions of the new request are
the same as or more comprehensive than the selection
conditions of the request to be deleted.
Thanks
Bhagesh

Process chians and process types Table

Hi all,
I'm looking for a table which can give me following details
Chain technical name and not LOG ID
Process Types
Process Technical names and not the ID
number of records in Infopackage
number of records in DTP
staus of each step (red/green/yellow)
status of the chain (red / green/yellow)
thanks for your help

You may start looking at these tables-
RSBKREQUEST DTP Request
RSBKREQUEST_V View of DTP Request
Process Chain Statistics Tables:
- RSPCLOGCHAIN, RSPCPROCESSLOG
Hope it Helps
Chetan
@CP..

Own process type in process chain

I have a meta process chain with three local process chains in it.
In the second local process chain i have an infopackage which only must be executed under special conditions. To validate those conditions i've made my own process type with possible events 'process ends succesful or incorrect'. If the process type returns 'incorrect' the infopackage will not be executed and the process chain continues with the next step. If the process type returns 'succesful' the IP will be executed.
So far so good.
During testing i found out that when the process type returns 'incorrect' all further actions within the process chain are executed as wanted but the local process chain gets status red in the meta chain. The third local process chain is not executed because it may only start when the second chain is succesful.
Questions:
Can i make my own possible events in a process type (green and yellow for instance)
Is there perhaps another way to solve this ?
Regards,
Chiel

Hi Tushar,
I read that document but it doesn't give me the solution !
I know how to make my own process type but i want other events to end the process type. Now i can only choose 'succesful' or 'incorrect'; i would like to have the value 'warning' (or something simular) too. Than the process chain doesn't get the status 'red' in the monitor and all follow-up processes will continue !
Regards,
Chiel

Further Processing Type In Process Chain

After adding the execute infopackage to process chain automatically DTP, Activate DSO and Furter Processing Variants come by with it .
Now, the data has to go to cube so Delete index etc will be added further, but do I need to have this further processing type or can I just delete it.
Whats it significance?

Hi
If you have given some job name in the infopackage schedule(background) statistically to track your job,then after completion of this job system doesn't know which process has to be run..so to connect between the next process we need to take this(further processing type) and give the name of the above job name in this process..
If you don't give the background job name statically..system creates a job with some name and it knows to identify the next process..
Hope it helps
Thanks
Teja

What are process types in process chain

hi any one tell me what are process types in Process chains

Hi,
In the Plan View of the process chain maintenance screen.
In the left-hand area of the screen, a navigation area is displayed. In the right-hand area of the screen, the process chain is displayed.
Use the drag-and-drop function to add the relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
If you insert into the chain a process that is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
Creating a Process Chain Using the Maintenance Dialog for a Process
You are in the maintenance dialog of a process that you want to include in a process chain.
1. Choose the Process Chain Maintenance pushbutton and create a process variant.
2. Save the variant and go back to the previous screen.
A dialog window appears in which you enter a technical name and a description of the chain that you want to create.
3. Confirm your entries.
The Add Start Process dialog window appears.
4. Create a variant for a start process.
1. a. On the Maintain Start Process screen, choose whether you want to schedule the chain directly or whether you want to start it using a metachain.
2. b. If you choose to schedule the chain directly, enter the start date value for the chain under Change Selections and save your entries.
The Maintain Start Process screen appears again.
3. c. Save your entries, return to the previous screen and confirm your entries in the Add Start Process dialog window.
You are taken to the Plan View of the process chain maintenance screen.
The various process categories, the application processes, and collection processes are displayed in the left-hand area of the screen. In the right-hand area of the screen, the process chain is displayed.
If the process that you used to create a chain is linked to additional processes, the respective process variants are generated and inserted into the process chain automatically. These variants are suggestions and can be changed, replaced or removed from the chain if required.
Only if the attribute realignment run is inserted automatically, do you also arrive at the variant maintenance screen.
If you want to specify yourself the processes that are to be included in a chain, choose Settings ® Default Chains, and select the Do Not Suggest Processes option. As a result, the system does not suggest, generate, or insert automatically any processes into the chain. This setting is user-specific.
If the chain that you create does not correspond to the standard, the system displays a warning. You can ignore these warnings if you are sure that you are creating a chain that meets your requirements. Warnings do not affect how the chain operates during runtime.
Your chain is checked in the checking view and during activation. The system tells you if it discovers any errors.
5. Use the drag-and-drop function to insert any additional relevant processes into your process chain.
You use the Process Types function to select the processes. This sorts the process types according to different categories. You can also call up InfoPackages and processes for the data target from the separate InfoSources and Data Targets navigation trees.
Additional Steps to Creating a Process Chain
6. When you add a process, you need to select a process variant or create a new variant. For collection processes, the system determines the variants.
Various functions for working with the process are available from the context menu:
Context Menu Entry for a Process Function Information
Maintain Variants With the exception of the variants in the collection process, you can use this function to change all process variants.
Exchange Variants You can swap the variants for an existing variant or a new variant.
Display Scheduled Jobs Once the process chain is active, you can use this function to display the jobs that have been scheduled.
Display All Jobs After at least one run of the process chain, you can display, for a specific process, all of the scheduled jobs for this process and all of the jobs with which this process was run. You arrive at the job overview from where you call up the relevant job log.
Create Message You can also send messages to an application process of the chain, depending on the success or failure of the process.
1. 1. From the context menu of a process, create an additional process variant of the Send Message type.
2. 2. If you maintain a message, first specify whether you want the message to be sent when the process has been completed successfully or unsuccessfully. Then choose Next.
3. 3. You arrive at a window, in which you can select an existing process variant or create a new one.
4. 4. If you create a new process variant, edit the document that is going to be sent, and maintain a list of recipients.
5. 5. Save your process variant and go back a step.
The message process variant is now assigned to your application process. When the message is sent, the status information and the process log can also be sent.
Wait Time
You use this function only to debug a process run.
Specify how long (in seconds) you want the delay to be between one event being triggered and the next process starting.
You can capture the process by using transaction SM37 (Job Overview) or SM50 (Process Overview).
Remove Process You use this function to remove a process from a process chain.
Manage Data Target You use this function in connection with the following types of process variants
1. constructing indexes
2. deleting indexes
3. constructing database statistics
4. rolling up filled aggregates
5. compressing InfoCubes
6. activating ODS object data
to call up the administration for each of the data targets.
7. Hold down the left mouse button to connect the processes through events.
Before you do this, select the process underneath the process type row, and position the cursor over the required process. When you select the process type row, the whole process is moved into the plan view.
From the context menu of a link, you can display the event or remove the link again. To do this, highlight the link and right-click with the mouse.
8. If necessary, specify whether you want the event to be triggered after the previous process has been completed successfully or unsuccessfully or whether you want the event to be triggered independently of the outcome of the process that precedes it.
9. Under Attributes ®Display Components assign a display component to the process chain.
10. Maintain additional process chain attributes if necessary.
11. Check your process chain in the Check View and make any necessary corrections.
The Legend explains the meaning of the different colors used to display the processes and links.
From the context menu for a process, you can display the messages resulting from the check.
12. Save your process chain if it does not contain any errors.
Result
Your process chain can be activated. After activation, the chain starts in accordance with the start process selections. For example, if you scheduled the start process directly and chose Immediately as the start date value, the chain run starts immediately after activation. In the Log View, you can display the reports for the chain runs.
Hope it helps.
Regards,
Amith

Error in Including Roll Up Process Type into Process Chain

Dear Experts,
On BI 7.0, I found an error, when including the Roll Up Process Type into my process chain. The sequence of my first process chain looks like this.
Start -> Execute Infopackage -> Execute DTP to load data to DSO -> Delete Cube Index -> Execute DTP to load data to cube -> Create Cube Index -> Roll Up
I found this error when activating the process chain
'No type "Delete Index" process can be in front of process "Roll Up of Filled Aggregates/BIA Indexes" variable ROLLUP_ZHRF_C04
Then, after looking through the forum, I found someone suggest using 'Initial Fill' before 'Roll Up'. I followed his sugguestion, so my second process chain looks like this.
Start -> Execute Infopackage -> Execute DTP to load data to DSO -> Delete Cube Index -> Execute DTP to load data to cube -> Create Cube Index -> Initial Fill -> Roll Up
The same message is shown; however, this time it just a warning message instead of the error msg.
1) How can I solve this problem?
2) In which sequence of process types I should take for my process chain?
3) Must I always use the Initial Fill before the Roll Up in the process chain?

Hello,
This issue is with patch 16 of BI. The only solution i think is you need to create a local chain with start process -> rollup and include all the roll up cubes in that variant and include this local chain at the end of the main chain. Hope this helps.
REgds,
Shashank

Create Process Chains and add Process Types using ABAP

Does anyone in here have experience in creating or changing a full Process Chain including the Process Types?
The reason is, that we have a lot of source systems with "similar" loads.
We already have an ABAP that can copy the chain and replace the InfoPackages. But we can't find a way to create/change a process, e.g. 'Hierarchy Save', 'PSA Delete' etc.
Any ABAP samples is highly appreciated!
Best Regards Jakob

Hello Jakob
did you find already this how to paper: "How to ... Implement custom process types" ?(https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/72e0e1ed-0c01-0010-74bc-b397c8c4dadc)
It has a code sample in the appendix.
Hope it helps,
regards
Martin
Message was edited by: Martin Lehmann

Decision between multiple alternatives process type

Hi All,
I want to use this process type "decision between multiple alternatives" in one of my process chains, but i want use this process type if the DELTA infopackage pulls ZERO records, skip the next process and more than ZERO records continue the process.
Please suggest me is it possible anyway.
Thanks a lot in advance.
Regards,
Ravi Kanth

Hi,
You can't do it with Decision type process as the conditions allowed are standard System conditions. As Suggested above, you need a code before that. The logic can be sketched as :
1. Load the provider.
2. Obtain the latest request in the provider.
3. Get the data from the request (std SAP prog is available for reading from providers).
4. Raise error upon getting no data (in this case you need to put the steps to be skipped in another chain and use in the main chain as meta chain).
--Akashdeep

The processing type?

Hi all,
I would like to create second delta load Infopackage for using it in Execute IP (Load Data) process type. What processing option do I need to choose? 'PSA and then into Data Targets' or 'Data Targets only'?
Thank you

Hi John,
here is the NOte details-
Symptom
You want to switch the upload procedure for an ODS object from full to delta. However, the delta initialization fails with a message indicating that there are already full uploads in the ODS object and therefore inits or deltas cannot be posted or activated.
Other terms
Delta; ODS object: delta initialization, RSM 098, full, Init
Reason and Prerequisites
If a full upload occurs once for an ODS object, you can no longer activate an init for the same DataSource/source system combination in this ODS object. The system does not check for overlapping selection conditions.
Solution
In the case if an ODS object, you can change the upload procedure from full to delta by subsequently marking the full requests that exist in the ODS object for this DataSource/source system combination as repair full requests.
These requests are therefore characterized by the fact that they can be posted into any data targets in any sequence. The repair full requests are never checked in a data target, that is, you can activate initializations and deltas (also with selections) in the ODS object. All ODS objects filled with these full requests behave as if the full requests did not exist in the ODS object.
Checks do not take place in all of these ODS objects.
Note the following:
Since the repair full requests are not checked, duplicate data records may be created or data may disappear if there is a subsequent init.
Since the repair full requests are not checked, you should take account of the extractor behavior, update modes, aggregational behavior of key figures and characteristics, among other things, when you are deciding whether you want to mark the full requests as repair full requests.
If you perform an init simulation after changing to repair full requests, make sure that no data is updated between the last full upload and the first delta upload.
Procedure for changing full requests to repair full requests:
After you import Support Package 19 (3.0B) or Support Package 13 (3.1C), the RSSM_SET_REPAIR_FULL_FLAG report is available which you can use to convert all full requests for a DataSource/source system combination that are in an ODS object into repair full requests.
Before you import this Support Package:
Use transaction SE16 to call the RSSELDONE table.
Here, enter an "x" in the "Repair_Full" field for all full request records that you want to mark as repair full requests.
CAUTION: This ONLY concerns those requests that begin with 'REQU_...'. The repair flag CANNOT be set for activation requests that begin with 'ODSR_'.
If the full requests still exist in the PSA, you can also use the scheduler under the 'Scheduler' menu option in the PSA tree (when you post from the PSA) to switch a PSA full request to a repair full request before loading.
If you load new requests with an InfoPackage, you can also assign the repair indicator to this full report.
it will tell u why u need to do the repair full request.
Regarding the Q3 u can put a Load process for ur Infocube.
Hope it helps-
MM

Processing types

Hi ,
wat are the difrent process types we have in process chains.
Regards,
Akhilesh

Hi Akhil,
Some of the process types are
ABAP Program
Execute InfoPackage
Read PSA and Update Data Target
Save Hierarchy
Delete Index
Generate Index
Activate ODS Object Data
Adjustment of Time-Dependent Aggregates
Attribute Change Run
Deletion of Requests from PSA
AND (Last)
Start Process
EXOR (First)
OR (Each)
regards
Srini

Custom Process Types not working in SAP BPC 10.0

Hi Experts,
We have migrated from SAP BPC 7.5 NW to SAP BPC 10.0 NW.
We have three Custom Process Types created in BPC 7.5NW using the super class CL_UJD_SIMPLE_ACTOR as super class.
It has been made Obsolete and Final class in BPC 10.0NW and the Custom Process types are not running as expected.
Can you please suggest if there is any alternative for using the existing custom process types? Or do we have any alternative for creating custom process types?
*Note: We have tried replacing the superclass with CL_UJD_ACTOR instead of CL_UJD_SIMPLE_ACTOR but of no use.
Regards,
Balraj.

Hi Inl,
The statement looks fine, just confirm:
Your CATEGORY dimension is named CATEGORY? Is it really has property COMPARISOIN?
Can you show the screenshot of UJKT run of script?
What is your core BPC SP?
Vadim

BI custom process type (ABAP OO Class): how to create a variant screen?

I created a custom process type in Netweaver 2004s (business intelligence) which in essence is nothing but an Abap class that implements certain interfaces. What I am now struggling with is how to write the code for the "new variant" input screen.
My understanding is that the logic has to be implemented in the method IF_RSPC_MAINTAIN~MAINTAIN, but I am lacking detailed information.
Can someone give me an example with a variant screen that displays two radio buttons?
Thank you,
D.

It is a custom class that implements the following interfaces:
IF_RSPC_GET_VARIANT
IF_RSPC_MAINTAIN
IF_RSPC_EXECUTE
The interface I am struggling with is the first one (get variant). Any more insight on how this should be used would be highly appreciated.
Thanks!

How to capture the process type for a particular application

In my application CRMD_BUS2000120 there are 3 process types namely incidents, zcomplaints and zrepair order. But all the 3 display the same description as New: Incidents . Since this is attached with the application name. How can i change the description according to the process type i select. If I select incidents the description should be Incident , if i select zcomplaints it should be zcomplaints. Can anyone guide me how to do this.
Thanks in Advance,
Anu

Hi Fred,
If you open any activities or opportunities, you can see the description if you select new button and click on the process type. It will be display Activities and below that New: Activity. Instead of always displaying the same description I want to override the description according to the process type. For me the application is not activity but Incident. Hope I am clear with the question.
Thanks,
Anu

Charateristic variable with Processing type "replacement path"

Hi all
I am using BI 7.0;
I have a characteristic ZPL_CNT in one dimensions of a Cube;
now i want to use the value of the ZPL_CNT as column in Query.
So i created a formula and a formula variable with replacement path of processing type:
setting:
i created a new formula "Calculated MBZ"
the formula variables is "ZMBZ" and inserted the variables into "Calculated MBZ"
Reference characteristic: ZPL_CNT
Processing type : Replacement path
Replace variable with: Attribute value
Attribute: characteristic Reference (constant 1)
But i find the value in Query incorrect
Can anyone help me solve this problem?
Thanks!

Hi Dragon,
Can you not drag and drop this characteristic directly in the columns...have I misunderstood something?
I think when you use replacement path in the formula variable , the fromula variable tries to find the reference characteristic value at each record level in the report and then replaces it with attribute value as defined and may be in your case as the characteristice is not defined in the row , it has problems to identify which value of the characteristic it has to replace.
Regards,
Sunmit.

InfoPackage Processing Type

Similar Messages

Maybe you are looking for