Skip to Content
author's profile photo Former Member
Former Member

SAPBPC7.5NW: DESTINATION APP LOGIC error

Hi All,

We are running on SAP BPC 7.5NW SP7. We have a business requirmement to transport data from Periodic Application to YTD application.

THe *DESTINATION_APP logic works as it is intended, except that the data ignores the signed data signs (/-). I.e. it transfer absolute figures. When we compare the cube data for each application, exact amount is transferred from source to target, except target is missing the (/-).

Is there something amiss? When we modify the script logic to filter value based on ACC.TYPE and multiply by factor of -1/+1, the data to target application is transferred correctly. Sample code as per below;

-Transferred correctly-

*DESTINATION_APP = CONSOL_BUDGET

*ADD_DIM GROUPS=NON_GROUP

*WHEN ACCOUNT.ACCTYPE

*IS "INC"

*WHEN TIME

*IS TMVL(0,%TIME_SET%) //January

*FOR %PER% = 0,1,2,3,4,5,6,7,8,9,10,11

*REC(FACTOR=(-1), TIME=TMVL(%PER%,%TIME_SET%))

*NEXT

/ -Transferred Errorneously

*DESTINATION_APP = CONSOL_BUDGET

*ADD_DIM GROUPS=NON_GROUP

*WHEN TIME

*IS TMVL(0,%TIME_SET%) //January

*FOR %PER% = 0,1,2,3,4,5,6,7,8,9,10,11

*REC(EXPRESSION=%VALUE%,TIME=TMVL(%PER%,%TIME_SET%))

*NEXT

/

Has anyone experienced this problem? Anyway to check where the error is occuring?

regards,

taj

Edited by: shameer84 on Jul 20, 2011 6:37 AM

Add a comment
10|10000 characters needed characters exceeded

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Jul 20, 2011 at 05:07 PM

    You answered your own question. I had the exact same problem not too long ago. Accounts that have ACCTYPE = INC store their values as the inverse of how they were input (e.g. input = 1000; stored in cube as -1000). You can see this if you pull the record from BW.

    So...

    1000 is input to ACCOUNTA which is ACCTYPE = INC in APPA. It is stored as -1000.

    Then you transfer it to APPB...

    Your script logic reads it as not converted -1000 and writes it to APPB as 1000 as because ACCOUNTA in APPB is ACCTYPE = INC.

    It is difficult to follow but long story short is that when script logic reads the value it doesn't convert it to the inverse but when writing it back it does on app tranfers.

    My code went like this....

    *IS "INC"

    *REC(EXPRESSION=-%VALUE%)

    *IS "EXP"

    *REC(EXPRESSION=%VALUE%)

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi Jonathan,

      So to summarize;

      There is nothing wrong with the DESTINATION_APP logic, and it is working as it is intended?

      I.e. We have to put in the signs when we write the logic?

      Account.Type INC = Factor(-1)?

      Seems odd - giving a scenario, when an income account is written as + amount, for purpose of reversal. In such instances, merely using INC= Factor(-1) will be erroneous.

      In my BW database

      Source INC written as : - 1000

      Target INC via DEST_APP: 1000

      It should not work this way as far as i know. We raised to OSS, they came back running the standard DESTINATION_APP logic catering same scenario and it does as per below;

      Source INC written as: - 1000

      Target INC via DEST_APP: -1000

      Which is correct.

      I understand the whole idea behind BW DB showing ➖ for INC but in the front end figure is still shows as positive amount, whilst expense is store and showed as ➕ figure.

      Correct me if i m wrong.

      But the way DEST_APP works, it seems a bit odd. In my opinion and if i m not mistaken the DEST_APP in MS/NW should just transfer the DB figures as read with (+/-) signs.

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.