Load Hierarchies using PSA

Hello,
We are trying to enable the sign reversal characteristic (0SIGNCH) for a hierarchy in order to reverse signs of certain accounts during extraction.
The documentation refers to the following prerequisites:
"...the hierarchy must have flexible hierarchy structures. This is the case when the hierarchy is loaded via the PSA and, as a result, has transfer rules."
"A hierarchy DataSource from a SAP source system must support loading by using a PSA."
How can we determine if the hierarchy datasource supports PSA loads? Example?
Is there a way to enable PSA loads for hierarchies?
Thanks,
Adam
How can we enable

Hi Adam,
I would NOT recommend tricking the system this way. The extractor needs to deliver different packages for IDOC and PSA and is not enabled to do this.
When the PSA method for hierarchies was introduced the development decided to enable this feature for only one extractor, I think it was EC-CS items or something similar because they wanted to make use of the new feature 'Signs on Nodes'. The other extractors were not changed and up to then there were no plans to change it.
If you need this you should contact development and ask for a solution. Maybe the problems aren't critical for 0COSTELMNT and you can change it, maybe they provide a solution with remote consulting, maybe they think your reasons are valid and they provide a note.
Best regards
Dirk

Similar Messages

How to load hierarchies using process chains

Hi ,
Can any one please explain the steps for loading hierarchies using process chain.whenever i drag the hierarchy infopcakage Save variant is also coming by default,so do we need to have different SAve variant for different hierarchy infopackages or can we have one save variant for all the hierarchy variables.
Thanks,
Vaka

Hello Veka,
How r u ?
Yes ! SAVE Variant & Attribute Change Run will add up while loading the Hierarchy InfoPackage.
Provide the InfoObject Name for which u r loading the Hierarchy in the SAVE variant and SAVE it. The same will be transferred to the Attribute Change Run also.
If u r creating the Chain with more InfoPackages then have the Save Variant & Attribute Change Run at the last.
Best Regards....
Sankar Kumar
+91 98403 47141

Loading Hierarchies using flat file

Hi experts,
I have requirement to load hierarchies using flat file.
I have to create hier on Person Responsible, sub nodes are Sales Office, Project Definition, Project Type and Project Definition Description. I have file, i need to load into BW.
I dont know much about hier loading, can you tell me what are the Attributes to be inserted and how to prepare the hier loading file which contains HIENM, VERSION, HCLASS, DATEFROM and DATETO.
I dont know these fields are enough to load my hier.
I have created one hier, when i try to activate it's giving error like ' no data exists'.
Can anyone tell me how to prepare file to load into hierarchy?
Thanks in advance,
Venky

Hi Venkatesh,
There are several formats to load a hierarchy via file. The following two are the commonly used formats.
1) Default
Node ID                     NODEID
InfoObject Name     INFOOBJECT
Node Name     NODENAME
Link Name     LINK
HghrLvlNode     PARENTID
Language Key     LANGU
Description - Short     TXTSH
Description - Medium     TXTMD
Description - Long     TXTLG
2) Sorted
Node ID                     NODEID
InfoObject Name     INFOOBJECT
Node Name     NODENAME
Link Name     LINK
HghrLvlNode     PARENTID
First Subnode     CHILDID
Next Node Along     NEXTID
Language Key     LANGU
Description - Short     TXTSH
Description - Medium     TXTMD
Description - Long     TXTLG
If Default format is used, the sequence of node IDs appeared in the flat file determines the structure of the hierarchy. Whereas the sorted hierarchy format defines the structure via PARENTID, CHILDID, NEXTID relationship.
You make the selection in DataSource/Tran.Structure tab of InfoSource Page by clicking on the "Hier. Structure button.
Good luck!
Bill

How to load hierarchie with IDOC as data transfer method

hi ,this is balaji, i have doubt.
can any one please explain, how to up load hierarchies using IDOCs. If any material provided could be helpful.And also give me what are the pros and cons.
regards
balaji.p

HI Balaji,
Check out the following link to load hierarchies:
http://help.sap.com/saphelp_bw33/helpdata/en/fa/e92637c2cbf357e10000009b38f936/content.htm
regards

Is a save step neccessary in a Process Chain when loading hierarchies with an ABAP program?

We are loading hierarchies using the ABAP routine found here in the SDN.
We have come accross the issue where the process chain loads successfully, but does not update the hierarchy (this problem is documented in the SDN). It is not a consistent issue, but it causes problems when it does occur.
OSS note 652856 points out that a SAVE HIERARCHY step is needed after the load and before the Change Attribute run.
We have added the step to the process chain, which leads me to the question.
In using the ABAP program to load hierarchies is the addition of the Save Hierarchy step necessary?
Will that resolve the issue with hierarchies not updating?

Hi Bill,
Yes, SAVE HIERARCHY step is required when hierarchies are loaded as part of process chain. This step ensures that the hierarchy data loaded to BW has been saved. Then we have to run ACR so that these hierarchies will be activated and adjusted.
This is the reason why even the hierarchy data loaded using infopackage needs this step. This step is not required if the Infopackage is triggered manually.
This link will help you in better understanding
http://help.sap.com/saphelp_nw04/helpdata/en/3d/320e3d89195c59e10000000a114084/content.htm
Regards
Chandu

How to load data from PSA to CUBE & DSO at a time using DTP in BI 7 ?

HI all,
I am new to BI 7 . How to load the data at same time to DSO & INFO CUBE using DTP.
Please provide me steps to load & plz specify which update mode I have to use ( FULL OR DELTA ) which one is best.
Plz Suggest me.
Thanks & Regards,
Kiran m.
Message was edited by:
kiran manyam

Below are the basic steps which we follow in any BI 2004S system:
1)Create datasource. Here u can set/check the Soucre System fields.
2)Create Transformation for that datasource. (no more update rules/transfer rules)
2.1) While creating transformation for DS it will ask you for data target name, so just assign where u want to update ur data.
DataSource -> Transformation -> Data Target
Now if you want to load data into data target from Source System Datasource:
1) Create infopackage for that data source. If you are creating infopackage for new datasources, it will only allow you update upto PSA, all other options u can see as disabled.
2)Now Create DTP (Data Transfer Process) for that data source.
3) NOw schdule the Infopackage, once the data is loaded to PSA, you can execute your DTP which will load data to data target.
If you are loading data from one one data target to other, no need to use PSA, you can directly execute DTP in that case.
Data Source -> Transformation (IP/DTP) -> Data Target1 -> DTP ->Data Target 2
Use the below link for detailed example:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/fc61e12d-0a01-0010-2883-e2fc63ef729b
Infosources are no more mandatory with BI 7.0, below is the link to scenarios where we use infosources:
http://help.sap.com/saphelp_nw04s/helpdata/en/44/0243dd8ae1603ae10000000a1553f6/content.htm
Full or delta depends on your requirement...
chk the below thread to know better
difference between the various loads
hope it helps
Message was edited by:
sriram viswanathan

Error in loading data from PSA to masterdataTables by using ProcessManually

Hello,
While loading Attribute master data to Masterdata tables, the data is loaded successfully to PSA but when I clicked process manually tab in the monitor screen to load the Attribute master data to Masterdata tables it is showing error.
Can anyone pls help me in solving this issue.
Thanks,
Soujanya

Hi Soujanya,
If it is a SAP BI 7 data flow, in order to load data from PSA to the InfoObject master data tables, you have to run the corresponding DTP.
On the other hand, if it is a SAP BW 3.x data flow, the InfoPackage should be configured so as to update data to subsequent targets (that is to say, the InfoObject).
Finally, take into account that if the DataSource provides duplicate records, the DTP or the InfoPackage (depending on the dataflow version) should be configured in order to deal with it. Otherwise, you could receive error messages during data load.
I hope this helps you.
Regards,
Maximiliano

How to load hierrarchies using dtp using flat file in bw ineed clear ste

how to load hierrarchies using dtp using flat file in bw ineed clear steps

Hi,
If you want to load InfoObjects in the form of hierarchies, you have to activate the indicator with hierarchies for each of the relevant InfoObjects in the InfoObject maintenance. If necessary, you need to specify whether the whole hierarchy or the hierarchy structure is to be time-dependent, whether the hierarchy can contain intervals, whether additional node attributes are allowed (only when loading using a PSA), and which characteristics are allowed.
1.Defining the source system from which you want to load data:
Choose Source System Tree ® Root (Source System) ® Context menu (Right Mouse Button) ® Create.
For a flat file, choose: File System, Manual Metadata; Data via File Interface.
2.Defining the InfoSource for which you want to load data:
Optional: Choose InfoSource Tree ®Root (InfoSources) ® Context Menu (Right Mouse Button) ® Create Application Component.
Choose InfoSource Tree ® Your Application Component ® Context Menu (Right Mouse Button) ® Create InfoSource ® Direct Update
Choose an InfoObject from the proposal list, and specify a name and a description.
3.Assigning the source system to the InfoSource
Choose InfoSource tree ® Your Application Component ® One of your InfoSources ® Context Menu (Right Mouse Button) ® Assign Source System. You are taken automatically to the transfer structure maintenance.
The system automatically generates DataSources for the three different data types to which you can load data.
      Attributes
      Texts
      Hierarchies (if the InfoObject has access to hierarchies)
The system automatically generates the transfer structure, the transfer rules, and the communication structure (for attributes and texts).
4.Maintaining the transfer structure / transfer rules
Choose the DataSource to be able to upload hierarchies.
Idoc transfer method: The system automatically generates a proposal for the DataSource and the transfer structure. This consists of an entry for the InfoObject, for which hierarchies are loaded. With this transfer method, during loading, the structure is converted to the structure of the PSA, which affects performance.
PSA transfer method: The transfer methods and the communication structure are also generated here.
5.Maintaining the hierarchy:
Choose Hierarchy Maintenance, and specify a technical name and a description of the hierarchy.
PSA Transfer Method: You have the option here to set the Remove Leaf Value and Node InfoObjects indicator. As a result, characteristic values are not transferred into the hierarchy fields NODENAME, LEAFFROM and LEAFTO as is normally the case, but in their own transfer structure fields. This option allows you to load characteristic values having a length greater than 32 characters.
Characteristic values with a length > 32 can be loaded into the PSA, but they cannot be updated in characteristics that have a length >32.
The node names for pure text nodes remain restricted to 32 characters in the hierarchy (0HIER_NODE characteristic).
The system automatically generates a table with the following hierarchy format (for sorted hierarchies without removed leaf values and node InfoObjects):
Description
Field Name
Length
Type
Node ID
NODEID
8
NUMC
InfoObject name
INFOOBJECT
30
CHAR
Node name
NODENAME
32
CHAR
Catalog ID
LINK
1
CHAR
Parent node
PARENTID
8
NUMC
First subnode
CHILDID
8
NUMC
Next adjacent node
NEXTID
8
NUMC
Language key
LANGU
1
CHAR
Description - short
TXTSH
20
CHAR
Description - medium
TXTMD
40
CHAR
Description- long
TXTLG
60
CHAR
The system transfers the settings for the intervals and for time-dependency from the InfoObject maintenance. Depending on which settings you have defined in the InfoObject maintenance, further table fields can be generated from the system.
The valid from and valid to field is filled if you select Total Hierarchy Time-dependent in the InfoObject maintenance. The time-dependent indicator is activated if you select the Hierarchy Nodes Time-dependent option in the InfoObject maintenance.
6.Save your entries.
Depending on which settings you defined in the InfoObject maintenance, additional fields can be generated from the system. Also note the detailed description for Structure of a Flat Hierarchy File for Loading via an IDoc and for Structure of a Flat Hierarchy File for Loading via a PSA.
Also find the below blog for your reference...
/people/prakash.bagali/blog/2006/02/07/hierarchy-upload-from-flat-files
You can load hierarchy using process chain...
Find the below step by step procedure to load hierarchy using process chain...
http://help.sap.com/saphelp_nw70/helpdata/EN/3d/320e3d89195c59e10000000a114084/frameset.htm
Assign points if this helps u...
Regards,
KK.
Edited by: koundinya karanam on Apr 8, 2008 1:08 PM
Edited by: koundinya karanam on Apr 8, 2008 1:09 PM

Load fails while running a Process Chain even before loading to the PSA.

Hi Experts,
We are working on BI 7.0 and ECC 6.0 on an IS-U Project.
We are loading Transaction Data using Process Chains. Data load is failing even before loading to the PSA and the error message is as below:
Error message during processing in BI
Diagnosis
An error occurred in BI while processing the data. The error is documented in an error message.
System Response
A caller 01, 02 or equal to or greater than 20 contains an error meesage.
Further analysis:
The error message(s) was (were) sent by:
Inbound Processing
Procedure
Check the error message (pushbutton below the text).
Select the message in the message dialog box, and look at the long text for further information.
Follow the instructions in the message.
Had anyone come across this type of error, if so, what could be the reason of failure and probable solution.
Your time is very much appreciated.
Thanks in Advance.
Best Regards,
Chandu.

Hi,
It might be a network connection between the source system and BW? Can you get your Basis colleague to look into the connection?
Hope this helps.
Cheers,
Gimmo

Urgent : Error while loading data from PSA to DSO

Hi,
I am working on 7.0.
When i look for data into PSA then i have 1 date field which is containing data in proper date format. This date field is mapped with 0CALMONTH & 0CALYEAR for which i have written routine and directly assigned to 0DOC_DATE .
I have written a start routine to do some modifications in SOURCE_PACKAGE.
But When i am loading data from PSA to DSO its giving below error:
" Exception wrong_date ; see long text RSTRAN 303
Diagnosis
An exception wrong_date was raised while executing function module
RST_TOBJ_TO_DERIVED_TOBJ .
System Response
Processing the corresponding record has been terminated.
Procedure
To analyze the cause, set a break point in the program of the
transformation at the call point of function module
RST_TOBJ_TO_DERIVED_TOBJ . Simulate the data transfer process to
investigate the cause. "
I am not getting why this error is coming up
pls guide me !!

you can map the code to DOC_DATE .
The code is used to read from any date and convert that into Fiscal year/period.
Try this code.
data: l_fiscyear type t009b-bdatj.
call function 'FISCPER_FROM_CALMONTH_CALC'
exporting
id_date = COMM_STRUCTURE-doc_date
iv_periv = 'V9'
importing
ev_fiscyear = l_fiscyear.
result value of the routine
RESULT = l_fiscyear.

How to Load Hierarchies from flatfile in BI7

Hello Gurus,
How to load Hierarchies from flat file in BI7
As when creating datasource in BI7,
IT GIVES FOLLOWING OPTIONS
TRANSCTION DATA
MASTER DATA TEXTS
MASTER DATA ATTRIBUTES...
ALL THESE WE BRING TO PSA LEVEL BY INFOPACKAGE AND SEND DATATARGET BY DTP...
But how about Hierarchies...
Looking for reply
Regards
Guru

Look at the below blog for step by step procedure :
Hierarchy Upload from Flat files
http://help.sap.com/saphelp_nw04/helpdata/en/fa/e92637c2cbf357e10000009b38f936/frameset.htm

Loading hierarchical dimension in planning

Hi,
I'm trying to load an Account dimension in Planning..
It is a flat table with the following levels. The table basically created P&l and balance sheet hierarchies..
L1 L2 L3 L4 ACCOUNTID ACCOUNTDESC
Do I need to convert this table in parent child format before loading it using ODI?
If not how do I load it in a flat format using ODI..
Any same query for converting it in parent child format will be helpful..
Any responses will be much appreciated!!

A simple way would be to have multiple loads L1, L2 then L2, L3..... or load the file into a table and create a view on it.
Cheers
John
http://john-goodwin.blogspot.com/

How to load data from PSA in BI 7.0

Hi,
Gurus
I'm trying to load data from PSA to my InfoObject masterdata but I can't get the change mode, so I change the processing to data Target.Right now its on PSA only
I will reward poaints
Regards
Alex

Hi,
I am just a beginner in 7.0, i had the same issue I loaded the master data in PSA but couldn't load in Data target i.e. info object (correct me if my understanding of your problem is wrong).
Try these steps:
1) Create and activate Transformation.
2) Create and activate DTP first then in DTP itself in <b>Execute tab</b> click "execute" ,go to infoobject right click on the info object you have created and select "maintain info object" , the datas will be loaded into info object
*Please assign points if useful.

Load hierarchical attribute dimensions with Integration Services?

Hi everybody,
I need to load product dimension which is organized in a relational table like this:
Product (parent_code, member_code, member_alias, brand, consolidation, formula)
Every product has a brand and I need to load brand as attribute dimension. The thing is Brand is not flat but it has it's own hierarchy. For Brand I have another relational table where data is organized parent-child like this:
Brand (brand_parent_code, brand_child_code, brand_child_alias).
I have used in the past Integration Services but with flat attribute dimensions.
Can I load hierarchical attribute dimensions with Integration Services? If yes, how do I do it, how do I specify the hierarchy?
Thank you,
Daniela

Graham,
This is definitely a supported feature in EIS/9.3.1/ASO. I have many models with this type of structure. How you set it up can vary. Usually my Attribute Hierarchies are not that deep, only two to three levels, maybe four in a rare case, so I don't usually use a parent child table to set up the hierarchy (I'm not saying that it won't work, it might, I haven't tried, but same steps should apply). In a typical model I will have my stock table which has a buyer field. Then in another table I will have my attribute structure which will have columns for buyer, teams, and categories.
In EIS OLAP model, you add your attribute hierarchy table and use a join to link it to the main stock table, joining on the buyer field (you are now going from a "star" schema to a "snowflake". Go into the properties and make sure you define all the columns as "Attributes".
Then in Metadata model, drag your categories attribute onto the outline, then drag the teams and set it as a child of categories and finally drag buyer and set as child of teams. You only set the attribute association for the buyer back to the base dimension.
When you run your dim build it will set up your attribute dimension correctly.
Some things to keep in mind, make sure you have a process that ensures for every stock code you have in the main table, you have a matching one in your attribute dim table.
Sometimes, depending on how much manipulation I need to do, instead of joining the tables in EIS I will go back to relational source and create a view that joins the two tables together, then in my OLAP model, I have one table that has three attribute columns, one column for the buyer and then the other two for team and category, from that point setting up in metadata model is the same.
Good luck, let me know if you run into trouble.

Loading hierarchies for 0GL_ACCOUNT InfoObject

Hi,
I cannot load hierarchies into 0GL_ACCOUNT InfoObject. I have created InfoPackage and in Update Data options I can only choose 'Only PSA' option. I have loaded attributes and texts without any problems. What should I do?
Regards,
Maciek

Hi Maciej,
Hope you had customized your 0GL_ACCOUNT hierarchy on R/3. Refer the below link
http://help.sap.com/saphelp_nw04/helpdata/en/6f/97a16a65fb11d3971c006094b969cf/frameset.htm
Bye
Dinesh

Load Hierarchies using PSA

Similar Messages

Maybe you are looking for