Scheduling a bpm process on particular date

Hi all,
I'm working on SOA suite 11.1.1.5 version.I want to scheduling a bpm process on 7th date of every month.Please give me a suggestion on this.
Thanks!

there are zillion of solutions, my favorite (I like primitive stuff, usually it works under all circumstances) is to use a cron job to run a WGET who triggers a HTTP enabled activator for the process.
Otherwise if you google for soa suite scheduler you will find endless discussions on this topic.... truth is that there is no simple solution AFAIK

Similar Messages

Reusing Human Tasks across BPM Processes with different Data Objects

Hi
JDeveloper 11.1.1.6, WLS 10.3.6, SOA/BPM 11.1.1.6
I have defined 2 BPM Processes, P1 and P2, which has 2 different Process Data Objects O1 and O2.
But I am reusing the same Human Task in both the processes.
For the Human Task to support the activities in both the processes, I have added O1 and O2 Data Objects in the Human Task Definition.
And hence the ADF Taskflow / page generated out of the Human Task will have both the Data Objects O1 and O2 as payload objects in the Page.
When an instance of Process P1 is created, the payload O1 will have values, but O2 will be null.
And when an instance of Process P2 is created, the payload O2 will have values, but O1 will be null.
It works well like this, but I am a bit concerned about the performance from BPM Process and also ADF page.
In ADF page, let us say, somehow I can control the rendering of the attributes or creation of the iterator bindings based on identifying which process is being executed.
(By setting the iterator binding refresh property in page definition)
In this way attribute bindings for O1 will not be created when P2 is being executed.
But still when the Process instance is created, and when we see the payload structure of the human task in the EM - Audit Trail,
I still see both data objects O1 and O2 are created in the Payload, but O1 will have nulls in process P2.
So my question is, from performance point of view, is it advisable to define different Data Objects in reusable Human tasks ?
Or should I have to define a separate Human Task definition which contains only the Data Objects related to the process it is being called from ?
Thanks for any help
Sameer

Martijn,
You are correct in your assessment that the JAG in the current JHeadstart release cannot cope with multiple bc4j packages. There is no work around for this. Upgrading to 9051 will not help.
In the JHeadstart-ADF release, this restriction has been lifted. You can place your EO, VO and AM objects in different packages, and you can group them in a separate project (Model project), while generating your JHeadstart application in a ViewController project.
We have a number of customers that use the latest JHeadstart-ADF builds to build their ADF apps. If you are interested in joining this beta program, please send an e-mail to [email protected]
Steven Davelaar,
JHeadstart Team.

Scheduling of BPM Processes

Hi,
   We have a scenario IDoc->XI->File. Here we are collecting IDocs from SAP-ISU system and doing N:1 mapping using BPM and writes into a single file. Here we do this by using a loop inside a block and the deadline
branch of the block we are saying duration of collect process as 4 hours. Now as per this logic the collection process will get triggered after the first IDoc hits the XI system.
   But the business requirement for this process is like in a day file should be send only once. i.e., we'll have to collect the idocs and send it in a single file w/o the wait time in our BPM but should be scheduled for a particular time in each and every day.
   Whats the best possible solution for the same? Pls do provide suggestions.
Thanks & regards,
Jayakrishnan

Hi Jayakrishnan,
plz choose in ur Deadline Branch for "Reference Date/Time" the value "Expression" and u can configure fixe dates.
Regards,
Udo

Data Association Between BPM Process Objects and EO,VO

Hi
I have an ADF screen where I am displaying values from database through EOs and VOs. My problem is after the user selects a value on the screen,I dont know how to map these selected values to BPM Process Data Objects.
Is there not a better way to achieving the below requirement.
"I have a dropdown on the screen.The value for the dropdown is being retrieved from a database table.After users selects a particular value from the dropdown, I have to map the value selected(including the rowset) to a BPM Data Object defined as a collection."
Please help.It is very urgent
Regards...

There are a few moving pieces to get the value of a field on a form changed when another field's value changes.
Look at the my blog on this from July using-database-driven-list-values-populate-bpm-variable (http://www.avioconsulting.com/blog/datwood/2012/07/02/using-database-driven-list-values-populate-bpm-variable). This goes into how to bind the BPM data object variables to a data source different than the default human task, set the autosubmit property, set the partitial trigger property and create the action binding you will need. Because you are not going to initialize your form with values when it first comes up, you just need to skip the "Initialize the ADF Form With Values Read from the Database" section.
Where I have you dragging over the "FirstName" and "LastName" name elements from the ADFbc data control, if you needed to populate BPM data object variables - you'd also need to drag these over into the form from the human task in the data control tab. Make the FirstName field autosubmit and then make your human task field have a partial trigger pointed to the FirstName field, then you'd be populating the BPM data object's element.
Know this is a lot to throw at you, but try getting the autosubmit working with the "listener" partial triggers and you should be able to get it going.
Dan

Oracle BPM Process Data mart

I am required to create audit reports on BPM workflows.
I am new to thid & need some guidance on configuring BPM Process Data mart. What are the pre-requisites for configuring it & what are the steps to do it.
Also, need some inputs on BAM database. What is the frequency of data upload. Is it data update or insert in BAM.

Hi,
You might want to check out the Administration and Configuration Guides on http://download.oracle.com/docs/cd/E13154_01/bpm/docs65/index.html.
I suspect you might find the BAM and Data Mart portions of this documentation a bit terse, so I've added the steps below that provides more detail. I wrote this for ALBPM 6.0, but believe it will still work for Oracle BPM 10g. It was created from an earlier ALBPM 5.7 document Support wrote called "ALBPM 5_7 Configuring and Troubleshooting the BAM and DataMart Updater.pdf.
You can define how often you want the contents in both databases updated (actually inserted) and how long you want to persist the contents of the BAM database during the configuration.
Here's the contents of the document:
1. Introduction
The use of BAM (Business Activity Monitoring) and Data Mart (or Warehouse) information is becoming more and more widespread in today’s BPM project implementations for the obvious benefits they bring to the management and tuning of processes.
BAM is basically composed by a collection of measurements of current processes load and execution times. This gives us an idea of how the business is doing at this moment (in a pseudo real-time fashion).
Data Mart, on the other hand, is a historical view of the processes load and execution times. And this gives us an idea of how the business has developed since the moment the projects have been put in place.
In this document we are not going to describe exhaustively all configuration aspects of the BAM and Data Mart Updater, but rather we will quickly move from one configuration step to another paying more attention to subjects that have presented some difficulties in real-life projects.
2. Creating the Service Endpoints
The databases for BAM and for Data Mart first have to be defined in the External Resources section of the BPM Process Administrator.
In this following example the service endpoint ‘BAMJ2EEWL’ is being defined. This definition is going to be used later as BAM storage. At this point nothing is created.
Add an External Resource with the name ‘BAMJ2EEWL’ and, as we use Oracle, select the Oracle driver, then click <Next>:
On the following screen, specify:
·     the hostname – here I have used ‘localhost’ as I am just setting this up to work on my laptop
·     the port for the Oracle service
·     the SID – here I have use Oracle Express so the SID is ‘XE’
·     the new user to create / use in Oracle for this database – here I have specified ‘BPMBAM’. This user, and its database, will be created later
·     the password for the user
Scroll down to the bottom of the page and click <Save>.
In addition to a standard JDBC connection that is going to be used by the Updater Service, a remote JDBC configuration needs to be added as the Engine runs in a WebLogic J2EE container. This Data Source is needed to grant the Engine access over BAM tables thru the J2EE Connection Pool instead of thru a dedicated JDBC. The following is an example of how to set this up.
Add an External Resource with the name ‘BAMremote’ and select the Oracle driver, then click <Next>
On the following screen, specify:
·     the Lookup Name that will be used subsequently in WebLogic - here I have given it the name ‘XAbamDS’
Then click <Save>.
In the next example the definition ‘DWHJ2EEWL’ is created to be used later as Data Mart storage. If you are not going to use a Data Mart storage you can skip this step.
Add an External Resource with the name ‘DWHJ2EEWL’ and select the Oracle driver, then click <Next>:
On the following screen, specify:
·     the hostname – here I have used ‘localhost’ as I am just setting this up to work on my laptop
·     the port for the Oracle service
·     the SID – here I have use Oracle Express so the SID is ‘XE’
·     the new user to create / use in Oracle for this database – here I have specified ‘BPMDWH’. This user, and its database, will be created later
·     the password for the user
3. Configuring BAM Updater Service
Once the service endpoint has been created the next step is to enable the BAM update, select the service endpoint to be used as BAM storage and configure update frequency and others. Here the “Updater Database Configuration” is the standard JDBC we configured earlier and the “Runtime Database Configuration” is the Remote JDBC as we are using the J2EE Engine.
So, here’s the example of how to set up the BAM Updater service….
Go into ‘Process Monitoring’ and select the ‘BAM’ tab and enter the relevant information (using the names created earlier – use the drop down list to select):
Note that here, to allow me to quickly test BAM reporting, I have set the update frequency to 1 minute. This would not be the production setting.
Once the data is input, click <Save>.
We now have to create the schema and related tables. For this we will open the “Manage Database” page that has appeared at the bottom of the BAM screen (you may have to re-select that Tab) and select to create the database and the data structure. The user required to perform this operation is the DB system administrator:
Text showing the successful creation of the database and data structures should appear.
Once we are done with the schema creation, we can move to the Process Data Mart configuration screen to set up the Common Updater Service parameters. Notice that the service has not been started yet… We will get to that point later.
4. Configuring Process Data Mart Updater Service
In the case that Data Mart information is not going to be used, the “Enable Automatic Update” checkbox must be left off and the “Runtime Database Configuration” empty for this service. Additionally, the rest of this section can be skipped.
In the case it is going to be used, the detail level, snapshot time and the time of update should be configured; in addition to enabling the updater and choosing the storage configuration. An example is shown below:
Still in ‘Process Monitoring’, select the ‘Process Data Mart’ tab and enter the name created earlier (use the drop down list to select).
Also, un-tick the Generate O3 Cubes (see later notes):
Then click <Save>.
Once those properties have been configured the database and the data structure have to be created. This is performed at the “Manage Database” page for which the link has appeared at the bottom of the page (as with BAM). Even when this page is identical to the one shown above (for the BAM configuration) it has been opened from the link in the “Process Data Mart” page and this makes it different.
Text showing the successful creation of the database and data structures should appear.
5. Configuring Common Updater Service Parameters
In the “Process Data Mart” tab of the Process Monitoring section -along with the parameters that are specific to the Data Mart - we will find some parameters that are common to all services. These parameters are:
• Log directory: location of the log file
• Messages logged from Data Store Updater: severity level of the Updater logs
• Language
• Generate Performance Metrics: enables performance metrics generation
• Generate Workload Metrics: enables workload metrics generation
• Generate O3 Cubes: enables O3 Cubes generation
In this document we are not going to describe in detail each parameter. But we will mention a few caveats:
a. the Log directory must be specified in order for the logs to be generated
b. the Messages logged from Data Store Updater, which indicates the level
of the logs, should be DEBUG for troubleshooting and WARNING otherwise
c. Performance and Workload Metrics need to be on for the typical BAM usage and, even when either metric might not be used on the initial project releases, it is recommended to leave them on in case they turn out to be useful in the future
d. the Generation of O3 Cubes must be off if this service is not used, otherwise the Data Mart Updater service might not work properly .
The only changes required on this screen was to de-select the ‘Generate O3 Cubes’ as shown in the last section.
6. Set up the WebLogic configuration
We need to set up the JDBC data source specified above, so go to Services / JDBC / Data Sources.
Click on <Lock and Edit> and then <New> to add a New data source.
Specify:
·     the Name – use the name you set up in the Process Administrator
·     the JNDI Name – again use the name you set up in the Process Administrator
·     the Database Type – Oracle
·     use the default Oracle Database Driver
Then click <Next>
On the next screen, click <Next>
On the next screen specify:
·     the Database Name – this is the SID – for me that is XE
·     the Host Name – as I am running on my laptop, I’ve just specified ‘localhost’
·     the Database User Name and Password – this is the BAM database user specified in the Process Administrator
Then click <Next>
On the next screen, you can test the configuration to make sure you have got it right, then click <Next>
On the next screen, select your server as the target server and click <Finish>:
Finally, click <Activate Changes>.
7. The Last Step: Starting Up and Shutting Down the Updater Service
ALBPM distribution is different depending on the Operating System. In the case of the Updater Service:
-     For Unix like Operating Systems the service is started or stopped with the albpmwarehouse.sh shell script. The command in this case is going to look like this:
$ALBPM_HOME/bin$ ./albpmwarehouse.sh start
-     For Windows Operating Systems the service is installed or uninstalled as a Windows Service with the albpmwarehouse.bat batch file. The command will look like:
%ALBPM_HOME%\bin> albpmwarehouse.bat install
After installing the service, it has to be started|stopped from the Microsoft Management Console. Note also that Windows will start automatically the installed service when the computer starts. In either case the location of the script is ALBPM_HOME/bin Where ALBPM_HOME is the ALBPM installation directory. An example will be:
C:\bea\albpm6.0\j2eewl\bin\albpmwarehouse.bat
8. Finally: Running BAM dashboards to show it is Working
Now we have finally got the BAM service running, we can run dashboards from within Workspace and see the results:
9. General BAM and Data Mart Caveats
a. The basic difference between these two collections of measurements is that BAM keeps track of current processes load and execution times while Data Mart contains a historical view of those same measurements. This is why BAM information is collected frequently (every minute) and cleared out every several hours (or every day) and why Data Mart is updated infrequently (once a day) and grows indefinitely. Moreover, BAM measurements can be though of as a minute-by-minute sequence of Engine Events snapshots, while Data Mart measurements will be a daily sequence of Engine Events snapshots.
b. BAM and Data Mart table schemas are very similar but they are not the same. Thus, it is important not to use a schema created with the Manage Database for BAM as Data Mart storage or vice-versa. If these schemas are exchanged by mistake, the updater service will run anyway but no data will be added to the tables and there will be errors in the log indicating that the schema is incorrect or that some tables could not be found.
c. BAM and Data Mart Information and Services are independent from one another. Any of them can be configured and running without the other one. The information is extracted directly from the Engine Database (PPROCINSTEVENT table is the main source of info) for both of them.
d. So far there has not been a mention of engines, projects or processes in any of the BAM or Data Mart configurations. This is because the metrics of all projects published under the current Process Administrator (or, more precisely, FDI Directory) are going to be collected.
e. It is also important to note that only activities for which events are generated are going to be measured (and therefore, shown in the metrics). The project default is to generate events only for Interactive activities. This can be changed for any particular activity and for the whole process (where the activity setting, when specified, overrides the process setting). Unfortunately, there is no project setting for events generation so far; thus, remember to edit the level of event generation for every new process that is added to the project.
f. BAM and Data Mart metrics are usually enriched with Business Variables. These variables are a special type of External Variables. An External Variable is a process variable with the scope of an Instance and whose value is stored on a separate column in the Engine Instances table. This allows the creation of views and filters based on this variable. A Business Variable, then, shares all the properties of an External Variable plus the fact that its value is collected in all BAM and Data Mart measurements (in some cases the value is shown as it is for a particular instance and in others the value is aggregated).
The caveat here is that there is a maximum number of 256 Business Variables per FDI. Therefore, when publishing several projects into a single FDI directory it is recommendable to reuse business variables. This is achieved by mapping similar Business Variables of different projects with a unique real Variable (on the variable mapping performed at publish time).
g. Configuring the Updater Service Log
In section 5. Configuring Common Updater Service Parameters we have seen that there are two common Updater properties related to logging. These properties are “Log directory” and “Messages logged from Data Store Updater”, and they specify the location and level of these two files:
- dwupdater.log: which is the log for the Data Mart updater service
- bam-dwupdater.log: which is the log for the BAM updater service
In addition to these two properties, there is a configuration file called ‘WarehouseService.conf’ that allows us to modify these other properties:
- wrapper.console.loglevel: level for the updater service log
- wrapper.logfile.loglevel: level for the updater service log
- wrapper.java.additional.n: additional argument to the service JVM
- wrapper.logfile.maxsize: maximum size of the updater service log files
- wrapper.logfile.maxfiles: maximum number of updater service log files
- wrapper.logfile: updater service log file name (the default value is dwupdater-service.log)
9.1. Updater Service Log Configuration Caveats
a. The first three parameters listed above have to be modified when increasing the log level to DEBUG (since the default is WARNING). The loglevel parameters have to be set to DEBUG and a java.additional.n (where n is a consecutive integer to the already used ones) has to be set to –ea to enable asserts, since without this option no DEBUG message is going to be generated.
b. Of the other arguments, maxfiles might need to be increased to hold a few more days of data when the log level is set to DEBUG (with the default value up to two days are stored).
c. The updater service has to be stopped, uninstalled, installed and then started for any of these changes to take effect.
Hope this helps,
Dan

How does the GR processing time affect the scheduling of the process order & the latest start date in the operation.

Hi
Can anyone explain how does the GR processing time affect the scheduling of the process order & the latest start date in the operation overview.

Hi
GR processing time means number of workdays required after receiving the material in storage.
Check this link:GR Processing time
Regards,
Anupam Sharma

BPM Process Data Object vs Managed Bean

I need to store an ID which is the primary key of a record in a database in my BPM process so that I can use that to set the bind variable on my view object query. Is it better to store this ID in a process data object or in a managed bean and why is one better than the other?

I suggest to do the other way.
Store the BPM Process Instance Id in the Database when you create data in the table.
Pass this Instance Id to the VO query parameters.
You can create a page binding of this instance Id from the Data Controls
I am assuming there is a 1-1 relation between your BPM Process and Database Row.

BPM process to manage business data vs Business Data in RDBMS

Hi all,
I have so far seen BPM as a pure business process tool rather than a data management one even thought BPM provides for managing data. If in case, we have a nice Business Process, which also collects plenty of related business data, what would be the suggestion?
1. To store Business Data in RDBMS and provide BPM with just enough info. for the process.
(or)
2. To store Business Data in BPM Business Catalog & do away with RDBMS (ofcourse BPM uses RDBMS for dehydration )
In our project, we are discussing this and some points in favour of approach (1) are:
i. For web based applications with multiple UI forms to collect data, storing data in RDBMS is way better on performance than accessing/storing in BPM business catalog
ii. Data Retention of Business Data in BPM needs special consideration which may lead to dumping data eventually in RDBMS
iii. UI frameworks help build UIs quick with a known data model rather than over APIs exposed by BPM
iv. Reporting over an RDBMS data model is easier than over a Business Catalog in BPM
Are these points valid or is approach (2) having other advantages to consdier?

I think I'm just backing up what you had on your original post, but here's what we typically tell customers when this comes up.
This has long been a best practice recommended by Oracle. In Oracle’s Performance Tuning for Oracle Business Process Management Suite 11g document , on page 17 it states:
"Minimize the amount of data stored in the process instance. Obviously, there is a tradeoff between the cost of storing data locally compared to storing keys and retrieving data for use within the process, which needs to be considered.
A reasonable starting point would be to model the process state to hold only values that are needed to control the process flow and keys to get any other (external) data on an ‘as needed’ basis. If retrieval is too frequent/slow, or the systems holding that data are not always available, then move more data into the process."
You touched on this, but decoupling the process payload and the underlying data for these reasons:
1. The underlying data and the processes typically have different lifecycles and need to be independent of one another
There is a need to maintain each at different times
They are typically modified by different groups of people with differing skills
The data stored in a database is typically the “source of truth” that sometimes must be able to be accessed and easily manipulated by applications outside of Oracle BPM; if stored as process instance data, instead of SQL extracting data from a database, the outside applications would need to access it through Oracle BPM APIs they are not necessarily familiar with
2. Lightweight process data persistence improves performance
The underlying message contract between the process instance and the engine that persists the payload should leverage key values where possible (think primary keys / relational keys from classic DBMS design patterns), rather than defining instance variables for every data element. The performance of the Oracle BPM engine is improved and the data for the instances are rendered faster.
The process instance is carrying the necessary process payload, rather than a bloated payload. Only the information germane to the current activity should be retrieved and rendered. This allows the application server to run more efficiently.
At each step in the process, the process payload is hydrated and then dehydrated (read from the engine’s underlying database tables and then written back to the tables). If this information is stored in an external database, there is no need for the overhead of this hydration and dehydration of large amounts of data to occur.
At each step in the process, if stored externally in a separate database outside of Oracle BPM, only the data required is read and / or updated when it is required to do so.
3. Decoupling helps speed development
Oracle BPM was built with the Decoupled Model View Controller (MVC) pattern in mind
One of its strengths is the architecture‘s business services layer that can make the source of the data transparent. Given a single key value stored in the process instance payload, services can be invoked from the process and the human steps in the process that represent the “real source of truth” that the business needs.
The MVC pattern’s model layer assumes that given the process’s key value, it is then possible to easily access underlying business data from a variety of sources including databases, EJBs and web services. Although storing all of the information inside the process payload can be considered one of the model’s business service sources, the overhead of using this in production systems is not recommended.
Once exposed, the business services can be reused by any business process needing the information.
User interfaces created with Oracle’s Application Development Framework (ADF) have out-of-the-box components and operations that take advantage of this MVC pattern. Some examples of these out-of-the-box patterns that do not have to be programmed include:
Database table information can easily displayed using Next and Previous that automatically retrieve the next or previous sets of rows
Similarly, scrolling in a table with many rows up and down renders data automatically
Both server and client side validations and rules
Database dropdowns and cascading dropdowns
Forms automatically created with Master / Detail patterns
4. Decoupling reduces the complexities arising from data synchronization
When orchestrating various external systems into a process, care must be given to account for “Systems of Record” and the purview these systems have over data values
Decoupling process instance data so that only key values are in the payload allow the Systems of Record to continually update the subservient element values without fear of stagnant data in the process
Participants in the process receive the most current data values when dealing with process instances
When data objects span several process instances, finding and updating data is easier if stored in a databaseExample: Process instance based on Orders. Several process instances may involve orders for a single customer. When the order changed, no problem, just find the process instance using correlations and updated it. When customer info changed, you need to synchronize any number of process instances. Placing the data in an RDBS made the solution simple. Simply updated the customer tables and all orders now have the latest info. No need to find related process instances and update them.
Some BPM events don’t carry sufficient information and need enrichment to process events. With data stored in the payload, there is no easy way to enrich the event data. This is especially true with ACM events. Events in ACM do not have instance information. Storing data in the database will prevent a costly work around using a dedicated process and correlations to get the info needed.
5. Decoupling facilitates the data capture for reporting and archiving
Keeping data in the BPM payload takes away the option to do custom reporting (outside of BAM) and archiving of business data.
Storing data in the RDBMS makes possible to create custom reports (outside of BAM) which would be not be possible or hard to do if all data lived in the BPM payload. Also, if you wanted to capture custom data changes or progressions thru a BPM and/or BPEL instance, RDBMS tables have a clear advantage over payload information. Payload (in most cases) would not have the data progression captured, and also reading data progression from the logs is not a recommended option.
Many organizations have data retention policy, which requires data to be archived and be accessible. Archiving and data accessibility is very limited if data is stored in the BPM payload.
6. The need for process Intelligence goes beyond the instance life cycle
Instances get cleaned up from process database and many organizations are interested in not only keeping the business data but also all the BPM related intelligence related to audit trail, KPIs etc. BAM data getting to BI cubes is one of the ways to ensure that intelligence lives on, but viewing process audit maps, audit trails and knowing what attachments were part of the process is a very common use-case. For the latter, the common patterns used are the use of UCM or other ECM products to store the correlated set of documentation that can be brought together in a Webcenter like content portal for historical research and auditability purposes. That, couple with an application database strategy to keep correlated application data would paint the full picture for the business users.
Hope this helps,
Dan

Data objects supported in the BPM Process Composer by Activity ?

Hi,
In BPMN 2.0 normalization, data objects are artefacts which show the reader which data is required or produced in an activity.
How is the data objects supported in the BPM Process Composer?
Thanks,
Grégoire.

Select the activity and then select the Data Associations button. You can associate existing data objects and create new ones.
Heidi.

How to Search BPM Processes for a Given Date Range through a VC Report

Hi All,
We have a VC component build to view the BPM process information. Here we are supposed to provide a Date range option for searching the processes. But the Range search is not working.
I tried in below ways.
1. On Action Submit, I set the Occurance_D value as "=DSTR(@DATE_FROM,"M/D/YY")&" - "&DSTR(DADD(@DATE_TO,1,"D"),"M/D/YY")" it is working only if there are processes existing either on DATE_FROM or on DATE_TO, otherwise its not working.
Like, I have 5 processes triggered on Sep-5-2011, then if i give the Date Range as 9/5/11 - 9/11/11 or 9/1/11 - 9/5/11 it is working. But if I give 9/1/11 - 9/11/11 it is not working.
I tried this way as well.
=DSTR(@DATE_FROM,"M/D/YY")&" : "&DSTR(DADD(@DATE_TO,1,"D"),"M/D/YY") . Even this is not working.
Can some one please help.
Regards,
SrinivaS

Dear SrinivaS,
The main things you need to consider are:
- store your date value from the UI in a store
- the store gets used to submit a filter string in format (MM/DD/YY) to
BI_START_TIME_D.
If you follow http://help.sap.com/saphelp_nw72/helpdata/en/81/541300d147
41b39057c8ab3be61f7a/frameset.htm
you find that the process data source can be filtered in format "9/9/11
- 9/12/11" for field BI_START_TIME_D and BI_END_TIME_D.
The trick is now at submission time to concatenate the strings
accordingly and submit to BI_START_TIME_D. Use the following dynamic
expression
=DSTR(store@START_DATE_FROM,"MM/DD/YY")&" - "
&DSTR(store@START_DATE_TO,"MM/DD/YY")
to format the string during submission. I was able to verify this on my
machine. I hope that also your locale settings work with this
implementation.
Find attached a link to a small sample application [(test_date.zip) |please find attached a small sample application (test_date.zip) which]which shows you the proper usage of a date picker in conjunction with the
process data source. Please import the zip file into VC and deploy it.
Best regards,
Ralf.

Getting Error/Note - Scheduling Falied ATP Processing error . Available date 15 may - while Booking SO

Hi All,
we are getting Note "Scheduling Falied ATP Processing error . Available date 15 may" - while Booking SO,
We have checked and found Data collection and ASCP plans also completed normal, and DB links are also fine.
Can there be anther reason for this?
Note - After changing the request date to 15 May also same error exists.
Regards

Hi Kumar,
We also faced same kind of issue where Instance was refreshed after data collection and DB links where not properly set, This can be one of the cause.
Regards

How to pass value object to BPM process and access process returned data

Hi,
I am new to Oracle BPM studio and gone through the tutorial. I did not find anywhere how to orchestrate the java components or ejb components or web services in BPM process. if any one provide sample business process orchestered with java component or ejb component or webservice, it will be great. Or atleast provide steps to do that.
Thanks and Regards
Mahesh Babu

There is a tutorial available online.. But you can always catalogue web services and JARs files into the ALBPM..
Just create a new module inside the Catalogue and then right click on it to see Catalogue Component and then select what component u want to add to ALBPM and then follows the steps of adding that component from your local machine and introspecting it..
If it is successful, then all the web-service methods or the JAR file methods would be catalogued into ALBPM..
You can put the WSDL address in the space provided for Web Services.. If password is required that too can be put..
Another way is to create a component in External Resources and then Cataloguing it...

"Scheduled for Outbound processing" message

Hi,
My scenario is: R/3 (IDoc Customer) -> XI -> PC (file) and I use a BPM with option "multi to single".
In the Message Monitoring, I have two steps:
1. Idoc DEBMAS06 --> BPM:
status = "Processed successfully". Thus it's ok.
2. BPM --> my PC:
status = "Scheduled for Outbound processing" and in column "outbound" I have not "IENGINE". There is no other error message and obviously no data are sent to my PC.
Have you already seen this message?
And have you a solution?
Note: Last friday, the same scenario was ok. I have just changed some data inside the mapping (occurence was not change).
Mickael.

Hi,
Try resetting the status to "Ready".
If you get SYSFAIL again, try deleting that particular LUW. If there are other messages waiting in the queue, just click on the unlock queue button and the remaining messages will flow thru.
Regards,
Sridhar

BPM Process chain takes long time to process

We have BI7, Netweaver 2004s on Oracle and SUN Solaris
There is a process chain (BPM) which pulls data from the CRM system into BW. The scheduled time to run this chain is 0034 hrs. This chain should ideally complete before / around 0830 Hrs. <b>Now the problem is that every alternate day this chain behaves normally and gets completed well before 0830 hrs but every alternate day this chain fails</b> there are almost 40 chains running daily. Some are event triggered (dependent with each other) or some run in parallel. In this, (BPM) process chain, usually there are 5 requests with 3 Delta and 2 full uploads (Master Data). The delta uploads finishes in 30 minutes without any issues with very few record transfers. The first full upload is from 0034 hrs to approximately 0130 hrs and the 2nd upload is from 0130 hrs to 0230 hrs. Now if the 1st upload gets delayed then the people who are initiating these chains, stop the 2nd full upload and continue it after all the process chains are completed. Now this entire BPM process chain sometimes takes 17 -18 hrs to complete!!!!!
No other loads in CRM or BW when these process chains are running
CRM has background jobs to push IDOCS to BW which run every 2 minutes which runs successfully
Yesterday this chain got completed successfully (well within stipulated time) with over 33,00,000 records transferred but sometimes it has failed to transfer even 12,00,000 records!!
Attaching a zip file, please refer the 21 to 26 Analysis screen shot.doc from the zip file
Within the zip file, attaching Normal timings of daily process chains.xls the name explains it.
Also within the zip file refer BPM Infoprovider and data source screen shot.doc please refer this file as the infopackage (page 2) which was used in the process chain is not displayed later on in page number 6 BUT CHAIN GOT SUCESSFULLY COMPLETED
We have analyzed:--
1)     The PSA data for BPM process chain for past few days
2)     The info providers for BPM process chain for past few days
3)     The ODS entries for BPM process chain for past few days
4)     The point of failure of BPM process chain for past few days
5)     The overall performance of all the process chains for past few days
6)     The number of requests in BW for this process chain
7)     The load on CRM system for past few days when this process chain ran on BW system
As per our analysis, there are couple of things which can be fixed in the BW system:--
1)     The partner agreement (transaction WE20) defined for the partner LS/BP3CLNT475 mentions both message types RSSEND and RSINFO: -- collect IDOCs and pack size = 1 Since the pack size = 1 will generate 1 TRFC call per IDOC, it should be changed to 10 so that less number of TRFCs will be generated thus less overhead for the BW server resulting in the increase in performance
2)     In the definition of destination for the concerned RFC in BW (SM59), the Technical Setting tab says the Load balancing option = No. We are planning to make it Yes
But we believe that though these changes will bring some increase in performance, this is not the root cause of the abnormal behavior of this chain as this chain runs successfully on every alternate day with approximately the same amount of load in it.
I was not able to attach the many screen shots or the info which I had gathered during my analysis. Please advice how do I attach these files
Best Regards,

Hi,
Normally index creation or deletion can take long time in case your database statistics are not updated properly, so can check stat after your data loading is completed and index generation is done, Do creation of database statistics.
Then try to recheck ...
Regards,
Satya

Processing large volume of idocs using BPM Processing

Hi,
I have a scenario in which SAP R/3 sends large volume say 30,000 DEBMAS Idocs to XI. XI then sends data to 3 legacy systems using jdbc adapter.
I created a BPM Process which waits for 4 hrs to collect all the idocs. This is what my BPM does:
1. Wait for 4 hrs Collect the idocs
2. For every idoc do a IDOC->JDBC Message transformation.
3. Append to a Big List
4. Loop at the Big list from step 4 and in the loop for
5. Start counter from 0 and increment. Append to a Small List.
6. if counter reaches 100 then send a Batch JDBC Message in send step.
7. Reset counter after every send.
8. Process remaining list i.e if there was an odd count of say 5300 idoc then the remaining 53 idocs will be sent in anther block.
After sending 5000 idocs to above BPM following problems are there:
1. I cannot read the workflow log as system does not respond.
2. In the For Each loop which loops through the big list of say 5000 idocs only first pass of 100 was processed after that the workflow item is not moving ahead. It remains in the status as "STARTED" but I do not see further processing.
Please tell me why certain Work Items are stuck is it becuase I have reached upper limit and is this the right approach? The Main BPM Process is also hanging from last 2 days.
I have concerns about using BPM for processing such high volume of idocs in production. Please advice and thanks in advance.
Regards
Ashish

Hi Ashish,
Please read SAPs Checklist for proper usage of BPMs: http://help.sap.com/saphelp_nw04/helpdata/en/43/d92e428819da2ce10000000a1550b0/content.htm
One point i'm wondering about is why do you send the IDocs out of R/3 one by one and don't use packaging there? From a performance stand point this is much better than a bpm.
The SAP Checklist states the following:
<i>"No Replacement for Mass Interfaces
Check whether it would not be better to execute particular processing steps, for example, collecting messages, on the sender or receiver system.
If you only want to collect the messages from one business system to forward them together to a second business system, you should do so by using a mass interface and not an integration process.
If you want to split a message up into lots of individual messages, also use a mass interface instead of an integration process. A mass interface requires only a fraction of the back-end system and Integration-Server resources that an integration process would require to carry out the same task. "</i>
Also you might want to have a look at the IDoc packaging capabilities within XI (available since SP14 i believe): http://help.sap.com/saphelp_nw04/helpdata/en/7a/00143f011f4b2ee10000000a114084/content.htm
And here is Sravyas good blog about this topic: /people/sravya.talanki2/blog/2005/12/09/xiidoc-message-packages
If for whatever reason you can't or don't want to use the IDoc packets from R/3 or XI there are other points on which you can focus for optimizing your process:
In the section "Using the Integration Server Efficiently" there is an overview on which steps are costly and which steps are not so costly in their resource consumption. Mappings are one of the steps that tend to consume a lot of resources and unless it is a multi mapping that can not be executed outside a BPM there is always the option to do the mapping in the interface determination either before or after the BPM. So i would sugges if your step 2 is not a multi mapping you should try to execute it before entering the BPM and just handle the JDBC Messages in the BPM.
Wait steps are also costly steps, so reducing the time in your wait step could potentially lead to better performance. Or if possible you could omitt the wait step and just create a process that waits for 100 messages and then processes them.
Regards
Christine

Scheduling a bpm process on particular date

Similar Messages

Maybe you are looking for