0PM_ORDER - WBS element not populated by extractor

Hi all
Just wondering if anyone has experienced a similar problem.
We use this data source as part of our PM master data loads. It runs every night, no problem. Iu2019m busy with a new user requirement regarding Project (WBS) costs as posted on PM orders, and I was pleased to see that 0PM_ORDER has field PROID (WBS) on it already u2013 thought I was half way to building my query!
Except, the field is not populated. Even when I run the extractor on the R/3 system to test (for an order type PM05 on which WBS element is a required entry), I never get any values in this field. I had a look on SDN and OSS and have seen a number of posts about the conversion exits relating to WBS elements, but this presupposes that a value is being populated in the extractor, which in my case is not happening.
Does anyone have any suggestions?
Regards, Lara

0PM_Order extracts the data of WBS element on the tab "location" on the PM order (IW33). It doesnt extract the WBS element on the tab "Additional data".
I am not sure how these WBS elements are different, your PS consultant might have an answer. Either you can have user exit to fill this field or ask your ECC abap consultant to fill the same in both fields of order, if doesnt make any difference. I am also in same situation, keep me posted if you have have get any new information from your PS consultant or SAP.

Similar Messages

WBS element not populating at item level

Hi Gurus,
 I am trying to create a new sales order using the function module SD_SALESDOCUMENT_CREATE but when i pass a value for the WBS element at item level it is not getting populated in the back end system.
 
 data :LT_RETURN TYPE TABLE OF BAPIRET2,
 LT_SALES_ITEMS_IN TYPE STANDARD TABLE OF BAPISDITM,
 LT_SALES_ITEMS_INX TYPE TABLE OF BAPISDITMX ,
 LT_SALES_PARTNERS TYPE TABLE OF BAPIPARNR ,
 LT_SALES_SCHEDULES_IN TYPE TABLE OF BAPISCHDL ,
 LT_SALES_SCHEDULES_INX TYPE TABLE OF BAPISCHDLX ,
 LT_SALES_CONDITIONS_IN TYPE TABLE OF BAPICOND ,
 LT_SALES_CONDITIONS_INX TYPE TABLE OF BAPICONDX,
 LT_SALES_CFGS_REF TYPE TABLE OF BAPICUCFG ,
 LT_SALES_CFGS_INST TYPE TABLE OF BAPICUINS ,
 LT_SALES_CFGS_PART_OF TYPE TABLE OF BAPICUPRT,
 LT_SALES_CFGS_VALUE TYPE TABLE OF BAPICUVAL ,
 LT_SALES_CFGS_BLOB TYPE TABLE OF BAPICUBLB ,
 LT_SALES_CFGS_VK TYPE TABLE OF BAPICUVK ,
 LT_SALES_CFGS_REFINST TYPE TABLE OF BAPICUREF ,
 LT_SALES_CCARD TYPE TABLE OF BAPICCARD ,
 LT_SALES_TEXT TYPE TABLE OF BAPISDTEXT ,
 LT_SALES_KEYS TYPE TABLE OF BAPISDKEY ,
 LT_SALES_CONTRACT_IN TYPE TABLE OF BAPICTR ,
 LT_SALES_CONTRACT_INX TYPE TABLE OF BAPICTRX,
 LT_EXTENSIONIN TYPE TABLE OF BAPIPAREX ,
 LT_PARTNERADDRESSES TYPE TABLE OF BAPIADDR1 ,
 LT_SALES_SCHED_CONF_IN TYPE TABLE OF BAPISCHDL2 ,
 LT_ITEMS_EX TYPE TABLE OF BAPISDIT ,
 LT_SCHEDULE_EX TYPE TABLE OF BAPISDHEDU ,
 LT_BUSINESS_EX TYPE TABLE OF BAPISDBUSI ,
 LT_INCOMPLETE_LOG TYPE TABLE OF BAPIINCOMP ,
 LT_EXTENSIONEX TYPE TABLE OF BAPIPAREX ,
 LT_CONDITIONS_EX TYPE TABLE OF BAPICOND ,
 LT_PARTNERS_EX TYPE TABLE OF BAPISDPART ,
 LT_TEXTHEADERS_EX TYPE TABLE OF BAPISDTEHD ,
 LT_TEXTLINES_EX TYPE TABLE OF BAPITEXTLI ,
 LT_BATCH_CHARC TYPE TABLE OF BAPIBTSEL ,
 LT_CAMPAIGN_ASGN TYPE TABLE OF BAPISDCA ,
 LT_CONDITIONS_KONV_EX TYPE TABLE OF KONV .
 
 DATA: LV_SALESDOCUMENT_EX TYPE BAPIVBELN-VBELN,
 LT_SALES_HEADER_OUT TYPE BAPISDHD,
 LT_SALES_HEADER_STATUS TYPE BAPISDHDST.
 
 DATA: LV_VALUE_SALESDOCUMENT TYPE BAPIVBELN-VBELN,
 LT_SALES_HEADER_IN TYPE BAPISDHD1,
 LT_SALES_HEADER_INX TYPE TABLE OF BAPISDHD1X,
 LT_SENDER TYPE TABLE OF BDI_LOGSYS,
 LV_BINARY_RELATIONSHIPTYPE TYPE BRELTYP-RELTYPE,
 LV_INT_NUMBER_ASSIGNMENT TYPE BAPIFLAG-BAPIFLAG VALUE 'R',
 LV_BEHAVE_WHEN_ERROR TYPE BAPIFLAG-BAPIFLAG VALUE ' ',
 LT_LOGIC_SWITCH TYPE TABLE OF BAPISDLS,
 LV_BUSINESS_OBJECT TYPE BAPIUSW01-OBJTYPE VALUE ' ',
 LT_TESTRUN TYPE TABLE OF BAPIFLAG-BAPIFLAG ,
 LV_CONVERT_PARVW_AUART TYPE BAPIFLAG-BAPIFLAG VALUE ' ',
 LV_STATUS_BUFFER_REFRESH TYPE BAPIFLAG-BAPIFLAG VALUE 'X',
 LV_CALL_ACTIVE TYPE CHAR4.
 
 DATA: WA_SALES_PARTNERS LIKE LINE OF LT_SALES_PARTNERS,
 WA_SALES_SCHEDULES_IN LIKE LINE OF LT_SALES_SCHEDULES_IN,
 WA_SALES_CONDITIONS_IN LIKE LINE OF LT_SALES_CONDITIONS_IN,
 WA_EXTENSIONIN LIKE LINE OF LT_EXTENSIONIN,
 WA_SALES_ITEMS_IN LIKE LINE OF LT_SALES_ITEMS_IN,
 WA_SALES_TEXT LIKE LINE OF LT_SALES_TEXT.
 
 LT_SALES_HEADER_IN-DOC_TYPE = 'ZSAL'.
 LT_SALES_HEADER_IN-SALES_ORG = '1000'.
 LT_SALES_HEADER_IN-DISTR_CHAN = '02'.
 LT_SALES_HEADER_IN-DIVISION = '01'.
 LT_SALES_HEADER_IN-PMNTTRMS = 'Z020'.
 LT_SALES_HEADER_IN-DUN_COUNT = '0'.
 LT_SALES_HEADER_IN-ADD_VAL_DY = '00'.
 LT_SALES_HEADER_IN-EXCHG_RATE = '0'.
 LT_SALES_HEADER_IN-BILL_DATE = SY-DATUM.
 
 data lv_kunnr type kunnr value '106475'.
 
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = lv_kunnr
 IMPORTING
 OUTPUT = lv_kunnr.
 
 WA_SALES_PARTNERS-PARTN_ROLE = 'AG'.
 WA_SALES_PARTNERS-PARTN_NUMB = lv_kunnr.
 APPEND WA_SALES_PARTNERS TO LT_SALES_PARTNERS.
 
 WA_SALES_PARTNERS-PARTN_ROLE = 'WE'.
 WA_SALES_PARTNERS-PARTN_NUMB = lv_kunnr.
 APPEND WA_SALES_PARTNERS TO LT_SALES_PARTNERS.
 
 WA_SALES_TEXT-ITM_NUMBER = '000010'.
 WA_SALES_TEXT-TEXT_ID = 'ZS01'.
 WA_SALES_TEXT-LANGU = SY-LANGU.
 APPEND WA_SALES_TEXT TO LT_SALES_TEXT.
 
 WA_SALES_TEXT-ITM_NUMBER = '000010'.
 WA_SALES_TEXT-TEXT_ID = '3010'.
 WA_SALES_TEXT-LANGU = SY-LANGU.
 APPEND WA_SALES_TEXT TO LT_SALES_TEXT.
 
 WA_SALES_SCHEDULES_IN-ITM_NUMBER = '000010'.
 WA_SALES_SCHEDULES_IN-REQ_QTY = '22'.
 APPEND WA_SALES_SCHEDULES_IN TO LT_SALES_SCHEDULES_IN.
 
 WA_SALES_CONDITIONS_IN-ITM_NUMBER = '000010'.
 WA_SALES_CONDITIONS_IN-COND_TYPE = 'ZMAN'.
 WA_SALES_CONDITIONS_IN-CURRENCY = 'NOK' .
 APPEND WA_SALES_CONDITIONS_IN TO LT_SALES_CONDITIONS_IN.
 
 WA_EXTENSIONIN-STRUCTURE = 'BAPE_VBAK'.
 * WA_EXTENSIONIN-VALUEPART1 = '090000000200'.
 APPEND WA_EXTENSIONIN TO LT_EXTENSIONIN.
 
 data lv_MATNR type MATNR value '000000000000000031'.
 
 CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 INPUT = lv_MATNR
 IMPORTING
 OUTPUT = lv_MATNR.
 
 WA_SALES_ITEMS_IN-ITM_NUMBER = '10'.
 WA_SALES_ITEMS_IN-MATERIAL = lv_MATNR.
 WA_SALES_ITEMS_IN-TARGET_QTY = '1'.
 WA_SALES_ITEMS_IN-TARGET_QU = 'ST'.
 WA_SALES_ITEMS_IN-SHORT_TEXT = 'TESST AJ'.
 WA_SALES_ITEMS_IN-SALES_UNIT = 'ST'.
 WA_SALES_ITEMS_IN-CURRENCY = 'NOK'.
 WA_SALES_ITEMS_IN-WBS_ELEM = '011215'.
 APPEND WA_SALES_ITEMS_IN TO LT_SALES_ITEMS_IN.
 
 DATA : WA_ORDER_ITEMS_INX TYPE BAPISDITMX.
 DATA : LT_ORDER_ITEMS_INXN TYPE STANDARD TABLE OF BAPISDITMX.
 DATA : WA_ORDER_HEADER_INX TYPE BAPISDHD1X.
 DATA : LT_ORDER_HEADER_INXN TYPE STANDARD TABLE OF BAPISDHD1X.
 
 WA_ORDER_ITEMS_INX-UPDATEFLAG = ' '.
 WA_ORDER_ITEMS_INX-ITM_NUMBER = '000010'.
 WA_ORDER_ITEMS_INX-MATERIAL = 'X'.
 WA_ORDER_ITEMS_INX-TARGET_QTY = 'X'.
 WA_ORDER_ITEMS_INX-TARGET_QU = 'X'.
 WA_ORDER_ITEMS_INX-SHORT_TEXT = 'X'.
 WA_ORDER_ITEMS_INX-SALES_UNIT = 'X'.
 WA_ORDER_ITEMS_INX-WBS_ELEM = 'X'.
 
 APPEND WA_ORDER_ITEMS_INX TO LT_ORDER_ITEMS_INXN.
 
 CALL FUNCTION 'SD_SALESDOCUMENT_CREATE'
 EXPORTING
 SALESDOCUMENT = LV_VALUE_SALESDOCUMENT
 SALES_HEADER_IN = LT_SALES_HEADER_IN
 * SALES_HEADER_INX =
 * SENDER =
 * BINARY_RELATIONSHIPTYPE = ' '
 INT_NUMBER_ASSIGNMENT = LV_INT_NUMBER_ASSIGNMENT
 * BEHAVE_WHEN_ERROR = ' '
 * LOGIC_SWITCH = ' '
 BUSINESS_OBJECT = ' '
 * TESTRUN =
 * CONVERT_PARVW_AUART = ' '
 STATUS_BUFFER_REFRESH = 'X'
 * CALL_ACTIVE = ' '
 IMPORTING
 SALESDOCUMENT_EX = LV_SALESDOCUMENT_EX
 SALES_HEADER_OUT = LT_SALES_HEADER_OUT
 SALES_HEADER_STATUS = LT_SALES_HEADER_STATUS
 TABLES
 RETURN = LT_RETURN
 SALES_ITEMS_IN = LT_SALES_ITEMS_IN
 * SALES_ITEMS_INX =
 SALES_PARTNERS = LT_SALES_PARTNERS
 SALES_SCHEDULES_IN = LT_SALES_SCHEDULES_IN
 * SALES_SCHEDULES_INX =
 SALES_CONDITIONS_IN = LT_SALES_CONDITIONS_IN
 * SALES_CONDITIONS_INX =
 * SALES_CFGS_REF =
 * SALES_CFGS_INST =
 * SALES_CFGS_PART_OF =
 * SALES_CFGS_VALUE =
 * SALES_CFGS_BLOB =
 * SALES_CFGS_VK =
 * SALES_CFGS_REFINST =
 * SALES_CCARD =
 SALES_TEXT = LT_SALES_TEXT
 * SALES_KEYS =
 * SALES_CONTRACT_IN =
 * SALES_CONTRACT_INX =
 EXTENSIONIN = LT_EXTENSIONIN
 * PARTNERADDRESSES =
 * SALES_SCHED_CONF_IN =
 ITEMS_EX = LT_ITEMS_EX
 SCHEDULE_EX = LT_SCHEDULE_EX
 * BUSINESS_EX =
 * INCOMPLETE_LOG =
 EXTENSIONEX = LT_EXTENSIONEX
 * CONDITIONS_EX =
 * PARTNERS_EX =
 * TEXTHEADERS_EX =
 * TEXTLINES_EX =
 * BATCH_CHARC =
 * CAMPAIGN_ASGN =
 * CONDITIONS_KONV_EX =
 .
 
 commit work.
 
 I am aware that there are other BAPI's available to create a new sales order(BAPI_SALESORDER_CREATEFROMDAT2 etc.) but the problem with using them is they internally call the same function module 'SD_SALESDOCUMENT_CREATE'. i have already tried to create the sales order using 'BAPI_SALESORDER_CREATEFROMDAT' but the effect is the same.
 When I pass WBS element value in VA01 and create a sales order I can see that WBS element value is coming correctly. But when i create the sales order using ABAP code WBS element is coming as blank. When I execute this standard FM it creates the sales order correctly with a blank against WBS element. I checked in the VBAP table the value is not even populated there . Kindly share your valuable inputs for the same.
- Akshay

May be you have to post this in ABAP forum to get suitable suggestions.
G. Lakshmipathi

WBS Elements not getting created in ECC Project System from CRM 7.0

Dear all,
We are trying to integrate SAP CRM 7.0 with SAP ECC-PS module. The objective is to bring in the marketing plan and elements data from the CRM system, and to create the corresponding WBS in project system. We have done most of the configuration as recommended by SAP in both the systems, and we see that the BDOCS are getting generated and sent to the ECC system. The following steps have been successfully completed:
1.       Set up the RFC connections between the two systems
2.       Selected the connection type as Middleware in CRM system.
3.       Installed the cProject Add on in CRM box.
4.       Created a project scenario (with project and network profiles) in the PS system and assigned the same in the CRM system.
5.       The Project Scenario in PS config has the same name as the Project Type in CRM config.
6.       Created and released the campaign ids being created in the CRM system.
As already mentioned, we can see that the BDOCS are coming to the ECC system and are getting stored in BDOC_TRACK table. However the issue is that the corresponding WBS elements are not getting generated in the ECC system. Is there anything that that we are missing in the ECC box which would trigger the WBS element creation?
Request you all to share your inputs which would be immensely beneficial for us in achieving this integration.
Thanks and Kind Regards,
Aditya Shrivastava

Hello Aditya,
We too are facing this issue.. if you have resolved the issue could you please let us know the solution ?
Some inputs related to our system,
We have upgrade from CRM 4.0 to CRM 7.0 SP07 and R/3 backend system is on 4.7 SP27, earlier we have completed the upgrade on sandbox without any issues which was upgrade to CRM 7.0 SP04 but with SP07 we are facing the problem of WBS Element not getting created in R/3.
Your help is highly appreciated.
Thanks & Regards,
Sumukh Kapoor.

TX CNS41 - settled cost from internal order to WBS element not displayed

Hi PS Expets,
I have a question regarding transaction CNS41 "Structure Overview" where cost settled from an internal order is not displayed in in the report for a selected project. This is in a ECC version 5.0
Settled costs from internal orders are posted with transaction type KOAO on WBS elements and when you check report RCNSTFCO you can see that the following transaction types are deselected when executing transaction CNS41:
delete t_rpsco_m where vorga = 'KOAO' "< insert
 or vorga = 'KOAL' "< insert
 or vorga = 'KOAP' "< insert
 or vorga = 'KOAQ' "< insert
 or vorga = 'KOAR'."< insert
CALL FUNCTION 'HFPM_RPSCO_TO_RPSCO_LIS_CONV'
This is implemented according to OSS note 51971 in order to eliminate internal business volume in the project structure when executing a PS hierarchy report.
But this also eliminate the display of the cost from the internal order.
Any ideas or a work around in order to display settled cost from an internal order on a WBS element in transaction CNS41
Kind regards,
Anne

Hello Tison.
I guess you have the Project created with a BAPI in your system in background. As far as I have seen I'd try the following in ABAP to create Partners in the Project Definition: BAPI_BUS2001_PARTNER_CREATE_M or the corresponding method ProjectDefinitionPI.PartnerCreateMultiple. This should happen in background when the Project is created also.
Best regards.
Jens Schmid

Worflow container elements not populating

Hi,
I am using a simple method and populating certain parameters of the method. in stand alone from swo1 the method populates the container element. This method is then called from a task in workflow.
The problem I face is that the workflow container elements are not populated, although the container elements at the task level are populated corectly in the workflow log. Even If I am binding a hardcoded value at the task to workflow binding level, the workflow container elements is not getting correct values; when I check the log and hence the workflow goes in error.
I would like to know why the workflow container elements not getting filled with right values. I have done many workflows before but never faced such an issue before.
Regards,
Vishal Bhatia
Edited by: Vishal Bhatia on Sep 19, 2011 2:33 PM

Hi,
I have checked the binding and workflow is activated again.
Also buffering was done in SWU_OBUF.
I also tried to run the workflow from SWDD itself and still the same problem. This is very strange. Never before i encountered such an error.
Kindly suggest. I also tried to create a new task and change the names of container variables in workflow. The strangest thing is the hardcoding of value also not being passed.
Types of parameters match and import export set accordingly.
Regards,
Vishal Bhatia

Input help for cost center & WBS element not working

Hi ALL
We are using SRM 4.0 with backend ECC 5.0.
Input help for attributes cost center (CNT), WBS element (PRO) are not functioning.
When tried to search for input help (F4) on the above attributes, I am getting message "Display not possible (Inconsistency in the input help)".
I even applied SAP note 746788 for cost center search help.
Can you tell me if I have missed any config settings?
Thanks in advance
Jagdish

Hi,
Did you managed the transactional RFC destination in the customizing (where you define all your log. systems it is an additional field in the table control).
Regards.
Vadim

Error during template allocation (CPTK) WBS element not found

Hello Gurus,
I tried to do template allocation
system is showing error WBS element xxxxxxxx does not exist
object type is - PR
object is - WBS
system is searching for field PSPNR of table PRPS as per the object type PR which is maintained in table TBO00 but during template allocation program it seems system is referring for POSID of table PRPS. hence the error.
Is there any note to apply? or any config I have missed ?
please guide
Thanks and regards
V.S.Natarajan

Hello Saurabh,
Thanks for your quick response
I checked both the notes created program as per note 149695 and there is no hierarchy error and applied the note 1853307 but still the same error exist
any other suggestion please
Thanks and regarsd
V.S.Natarajan

Project stock (WBS element) not consider in QA07 Transaction

Standard SAP transaction QA07 for Deadline monitoring of batches not
considering project stock (WBS element) for the same
Kindly suggest for your possible solutions as we are going to fully equipped with
project system and its stock must be
considered for background scheduler of recurring inspection
Waiting for your kind and immediate action
With Regards,
Kunal Sheth

Hi!
We regret to inform you, that the report RQAAAS10 ( QA07 ) does not
support project stocks.
For better understanding of the transaction QA07, I would ask you kindly
to review the documentation for the report RQAAAS10.
Here are the Requirements for this report:
'The batch master data corresponds to the selection conditions.
Only those batches that full fill the following conditions are examined:
-the batch status is "released".
-the unrestricted-use stock is greater than zero.
-the stock is not in a HU storage location'
This means that all 'special' stock locations, like for example project
stock, will be not relevant for this transaction.
Unfortunately SAP not able to provide a workaround for your
issue, with the exception of a customer own development. In this case
you can copy the report and make the correspondent adjustments needed.
Best regards
Erika

WBS element not updating in additional data of IW32

Hello, We have created a sales order with account assingment as WBS element. From this line service order will be created, but when we check the service order additional data, the wbs element field is showing as blank. What is the reason for this.

AbhayDev,
Please Let us know your observation and Solution
Babu

Standard Container element not populating....

Hi All,
I am using a standard task TS17900100 to process the HCM Form in workflow at 2 places. There is a standard container element STEP_OBJECT of this task which gets populated at run time.
Now at first place this container is getting populated correctly. But in the second place I have used the same binding and same task but STEP_OBJECT container is not getting populated. Also, STEP_OBJECT is not an import/export parameter.
Please suggest.
The task is using the following class and method :
CL_HRASR00_WF_COMPONENTS
WI_EXECUTION_VIA_R3_INBOX

Hi,
I have checked the bindings in both the steps. It is same and all the containers are getting populated in the log except STEP_OBJECT. That's why I am not getting the reason for such a case. STEP_OBJECT is getting populated by itself in the first step. But it is not getting populated in the second step.
Please suggest.
Regards,
Guddan

WBS elements not deleted from PRPS table

Hi Experts,
In CJ20N transaction:
When I delete a project with project profile (ZABC):
- The project record is completely deleted from 'PROJ' table.
- The WBS records are completely deleted from 'PRPS' table.
When I delete another project with different project profile (ZXYZ):
- The project record is completely deleted from 'PROJ' table.
- The WBS records are NOT deleted from 'PRPS' table.
What is the reason for not deleting records from PRPS table?
Thanks in advance for your valuable answers.

WBS should be having actuals.

TECO Status in WBS ELement not allowing DP91 transaction for RRB

Hi Team,
I would like to look if DP 91 will not allow to Bill a particular cost once the project is in TECO Status.
Please confirm if this is configurable.
Regards
Vignesh R

Thanks for your clarification.
I have one more query which is not related to the Project status.
When a Dynamic item is being populated in DMR after DP91 transaction,the summarisation of material or activity takes place and If there are A(50$),B(25$),C(25$) are the materials posted and grouped to form Dynamic Item "Material" and E(100),F(50$),G(50$) are the activity posted and grouped to form Dynamic item "Labor" based on grouping set in material determination,
the DMR will reflect as
Line               item 10
Material         Material
Price             100$
Line                item 20
Material          Labor
Price              200$
My client need a report which would give a detailed list of Dynamic item along with quantity and value by just entering the Billing document number.
Like
Material
A   50$
B   25$
C   25$
Labor
A 100$
B 50$
C 50$
What are the tables I need to refer to bring up a report as stated above.
I couldnt get these details in AD01DLI and AD01DLIEF
Regards
Vignesh R

CADO Report - Missing Project Definition and WBS elements

While running CADO (time sheet data) report for employee, data is not being pulled up for the WBS Element and Project Definition. What could be the reason? Here time is entered against a network activity but for some entries WBS element and project definition is dispalyed and for remaining it is not.

Yes....these activities are assigned to the WBS element in the project. As I mentioned earlier for the same activity in some cases WBS element is populated.

WBS Element extraction from R3

I have created a new extractor for Materials Management and when I extract 'WBS Element', it appears in BW as a number eg. C/LS/0019.01 in R3 appears as 1441 in BW. I extract WBS Element from other areas of R3 and map to the same WBS Element InfoObject in BW and these appear OK. Is there some kind of conversion routine I need? The WBS Element appears OK in RSA3. The table in R3 is EKKN.

The WBS Element I am extracting is a numeric field of length 8, whereas the WBS Element in my Projects extractor is a characteristic with length of 24 - there is a conversion routine on the Projects InfoObject. However, the numeric field appears ok in RSA3 and when I create new InfoObject with no conversion routine, the field is just populated with a 3 or 4 digit number. Which conversion routine would I need to apply to view this OK in BW? As it appears in the extractor OK, I just need a little help with the conversion routine.
Also this is the only WBS Element available in the tables I need to extract from - there is no external one available.
Thanks is advance guys!
Scott

FBL5N with WBS element

Hi All
I would like to display line with WBS element number in FBL5N but wbs is not populating.
Eventhough the selection wbs option is available in layout but not populating since WBS asscociated with revenue account not customer.
WBS element is assigned to revenue account not to the customer.
Is that a way where i can view the report with customer and WBS element number
Please advice
Thanks
Bali

Dear,
It is difficult to populate WBS Element/Cost center in the Customer Line Item because of revenue determine no. of WBS elements to single Customer Line item.
Regards,
Kishore

0PM_ORDER - WBS element not populated by extractor

Similar Messages

Maybe you are looking for