cancel
Showing results for 
Search instead for 
Did you mean: 

BPC - Splitting P&L from Main logic

Former Member
0 Kudos

Hi All,

We have a BPC solution with 6 applications. Ultimately all applications will post data to P&L Application. If there are multiple users on the system at the same time working with different applications (or same application), when everyone is trying to post data into P&L at the same time, System is becoming incredibly slow (because of concurrency locking). We are looking at splitting P&L off and running it as a background job and at this stage understand that no users will be allowed in the system or at least send data while this P&L background posting is running.

What I would like to know is; is anyone else out there doing this and how do you manage it as a process?

Running it overnight is fine of course but how do you achieve updates during the day, we have tight deadlines and I know this will be a requirement.

BTW, we are using Custom logic BADI (ABAP code) for posting data into P&L. Would it be better (in terms of performance), if we use script logic?

Thanks in advance.

Raj

Accepted Solutions (0)

Answers (1)

Answers (1)

krishna_priya1
Contributor
0 Kudos

Instead of posting to P&L application , what ever needs to be posted to P&L can be calculated & saved in respective applications in an another datasource ,for example PL, during the day . And in the night , this data can be copied to P&L application .

Hope this helps.

Former Member
0 Kudos

Hi Krishna,

Thank you for your reply.

One of the business requirement is that they can't wait unitl end of the day to view latest P&L data. So we thought of doing update it every 20 mins. But, at the time of updating, no one can use the application because the cube will not allow to post data into it. Any other way to achieve this?

Raj

Former Member
0 Kudos

Hi Raja

You could use DestinationApp instead of BAdis, that way you don't have to switch the cube to loading

Former Member
0 Kudos

Hi Sabine,

Thank you for your reply.

Could you please explain me what do you mean by using 'Destination App' insted of a BADI? I didn't get your point.

A bit more detailed information would be highly appreciated.

Thanks & Regards,

Raj

Former Member
0 Kudos

HIiRaja,

Destination App is a standard programme that can be called via script logic.

In 7.0 you had transport a BAdi but in 7.5 it's standard.

It basically allows you to push records from one BPC cube to another and is triggered by a Datamanager package.

If you do a search on Destination App you should find a lot of code examples for this.

here is the link to the how to guide for 7.0 but remember for 7.5 the transport is not needed - so only look a the script logic part.

http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/e04b5d24-085f-2c10-d5a2-c1153a9f9346

I think the syntax is slightly different too, so you will have to test it out

Former Member
0 Kudos

Hi Sabine,

Thank you for your suggestion.

We tried that option and felt that it makes no difference in terms of time. I strongly believe the problem we have got is not because of the technique we are using (BAPI / Script logic) but because of concurrent locking. Since everyone is trying to push data into P&L cube at the same time, we are experiencing such an issue. We are looking for some sort of solution to avoid this clogging of P&L. Any ideas on this ?

Thanks & Regards,

Raj

Former Member
0 Kudos

maybe you just need to revisit your business process.

all departments could enter their information into the relevation applications. and then the actual transfer into the P&L app could be an admin task that only one person (or one team) looks after, and they can just go through each application one after the other?