WBS element in VA01

Hi,
I want to make WBS element as required field in VA01 transaction.
I tried in SHD0, but i could't make it required.
Could anyone tell me the what transaction variant I have to choose.
Regards,
Chandra

In the document type, check the checkbox Incomplete.messages. But this will apply for not only one field but all incomplete items.
Even with SHD0 also it should be possible to make the field as mandatory. As a last resort you can use exit in MV45AFZZ for changing the screen field to mandatory.
Regards,
GSL.

Similar Messages

WBS element for Sales Order Item level

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit
Edited by: Satyajit Saha on Feb 22, 2008 1:24 AM

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit
Edited by: Satyajit Saha on Feb 22, 2008 1:24 AM

In credit memo request " WBS element"

hi,
while creating credit memo request in va01 it is asking complete data "WBS Element" in item data accounting mgmt it has WBS element .i think its not relevant for SD
Regards
kiran.c

Hi,
Check out the Item category settings, U might have activate the special stock indicator Q in VOV7.
But technically if your credit memo request is with respect to some sales process which is related to Project and is triggered through project systems , ideally you would like to want to have the wBS element so that it gets upadted in the project report. Check out with the Client and then create a WBS element which is billing relevant. Otherwise it will throw up an error at the time of saving the billing document and the accouting document will not get generated.
If you dodnot want the credit memo detaisl to be updated at the project level remove the special stock indicator from the Item category of the Credit memo
Hope this helps you to solve the issue.
Thanks & Regards,
Nithin

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

Segment for WBS element in Inbound Sales Order Idoc

Hi gurus,
I am trying to create an inbound idoc for sales order ' VA01'. I need to populate WBS element in the item level under Account Assignment Tab. I am using ORDERS05 basic type. Please help to find which segment to use for WBS element. Waiting for your reply. Please help.
Regards,
Satyajit

Hello,
        As far as I know, there is no Segment / Field definition in ORDERS05 for WBS Element as it is not mandatory information to be filled in order for the Sales Order to be Complete. So, you need to create an Extension of the IDoc Type ORDERS05. For your requirement, here is the Approach I have.
1. Create an extension for IDoc Type ORDERS05 to ZORDER05 with a Custom Segment Z1EDP01 in which you'll have the Custom Field Name VBAP-PS_PSP_PNR which is the WBS Element field in VBAP Table.
2. Now, use the Customer Exit EXIT_SAPLVEDA_001 in the Enhancement VEDA0001 in which you can actually populate the Field WBS Element that would be already available in the Inbound IDoc to store it in a Work Area. As you are aware, you'll need to create a Project in CMOD for the same.
3. Export the same to some MEMORY ID 'XXX'.
4. Come back to the Selection Program for ORDER05 which is IDOC_INPUT_ORDERS in which you'll find the below CASE Statement.
    CASE xaprau.
          WHEN ' '.
            PERFORM call_va01_new_orders USING ok.
          WHEN 'Q'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Angebot
call transaction Order Entry VA01 with refer to quote number.
            PERFORM call_va01_new_orders_angbt USING ok.
          WHEN 'C'.
Aufruf Transaktion Auftragerfassung VA01 mit Bezug auf Kontrakt
call transaction Order Entry VA01 with refer to contract number
            PERFORM call_va01_new_orders_contk USING ok.
          WHEN 'L'.
5. Now, since our Standard Order Type (VBAK-VBTYP) is 'C',
    we'll have to choose the Subroutine for the 'C' Option.
6. In this Subroutine, there is another Subroutine va01_dynpro_kopf_kaufmann_kde2 which is for populating Custom Dynpro Fields for the Sales Order. So, we need to choose the same Subroutine inside which we have to Create an Enhancement Implementation.
7. In this Enhancement Implementation (Implicit), we have to IMPORT the value of the WBS Element which was exported in the Customer Exit.
8. Check if it is initial. If it is not, then Call the Perform as below.
     IF NOT WA_Z1EDP01 IS INITIAL. "Checking if the Segment
                                                       " is Empty
   PERFORM DYNPRO_SETZEN USING 'COBL-PS_POSID' WA_Z1EDP01-ZZWBSELEMENT.
ENDIF.
9. Since the Sales Orders are posting using BDC here, by calling the above Subroutine DYNPRO_xxx, we are appending our Custom Segment / Field value to the BDC_DATA table.
10. In Step 8, I've given the Notation for Work Area. It will also be applicable when there are multiple Line Items. All you have to do is to EXPORT an Internal Table instead of Work Area and use the same here for each Line Item.
11. I've given you above procedure because I've worked on similar requirement in which I had to populate the Special Processing Indicator instead of WBS Element.
Hope it would be helpful for you.
Thanks and Regards,
Venkat Phani Prasad Konduri

WBS element naming problem

Hi,
I have created one standard proyect where:
Proj. Def. : Z/123456
WBS element: Z/123456-000-1
Mask: Z/000000-000-0
SD/PS assignmnt: set.
It is working properly, so if I create sales order 356 It creates project Z/000356 and WBS element Z/000356-010-1 for first position, Z/000356-020-1 for second position and so on.
The thing is that I would like these WBS elements to be named in this way:
Z/000356-material_serial_number
or just
material serial number
where material_serial_number is the serial number assigned to the material in the corresponding position in VA01 (there is only 1 unit of this material in each position in the sales order).
How should I proceed??
Thanks in advance.
Luis

SO number would be the numbered to the project def in Assembly Processing, but a material with in a SO cannot be assigned has number to the project def.

Generate Plan Order from MRP Run (MD51) by WBS Element

Dear All,
1. I have created sales order with assigment WBS element (VA01)
2. Then I created Routing & BOM for Material (CA01 & CS01)
3. Generate MRP Run (MD51)
The problem the generated mrp run doesnt consume planned order .. i have set the planning strategy 21 or 40, but still doesnt works.. is there any other parameter that i should configure..???
Help Me...
MamaRara

Hello,
Hopefully, the following link can assist you.
- Re: After firming planned order, new planned order is generating in MRP run
- Basic Scheduling in MRP run
- Re: MRP run
- During MRP run unwanted plant and storage location include and exclude
- MRP run does not consider the common stock
Thanks & Regards
JP

Error no WBS billing element found while substituting WBS element 00050923

Hi,
Please give me some quick solution to overcome this error in my IDES. I have seen the note, sap help and othe rsuggession . could not get rid of this error.
Quick response is requested.The earlier thread was also unanswered.
Zinni

sales order having account assignment at item level as WBS element. No substitution exist in sales side too. I went through the sapnote_0000499389. Still could not identify the reason of error.
As further adviced by SAP , I have checked following notes, still problem could not be solved.
672929 No billing because of error VF156
499389 VA01/VF01: Check/derivation of the assigned WBS element
Zinni
Edited by: Makwana Zinni on Oct 19, 2009 6:03 AM

Strategy 92 don't consumption the Pir for WBS element

Dear Gurus,
i insert in the material master MRP3 the group strtegy 92 (Planning with final assembly).
After we insert in the MD61 the planned indipendent requierement whit the transaction MD61 and
we set the field "Acct Asst Cat" = Q and the insert the WBS Element.
After when whit the transaction VA01 we create the sale order position whit the same WBS element the system
don't consumption the Pir , but propose the double quantità to product.
I need use the WBS element in the Pir and in the Sale order but i need to consuption the Pir quantity whit the sale order quantity.
There is the customizing settinG?
Thanks a lot
Daniele PIstilli
PP TEAM

HI,
Check your planning strategy 92 in
IMG>production>production planning>demand management>PIR-->Planning startergy-> Define stratergy
Check for your Strategy 92
Reqmt type of independent reqmts
Is consumption is set as 1?
and also check
Reqmt type of customer reqmts
is Allocation Indicator is set as 1?
IF Not
maintain in OVZG for your Requirement Class specified in strategy for customer requirement
for PIR Requirement Class maintain the setting In OMPO

Which field matches to the WBS element

Hi,
I am doing an interface program, in that I need to populate the WBS element in trasaction VA01 under the tab Account Assignment. I am using the BAPI 'BAPI_SALESORDER_CREATEFROMDAT1'.
Let me know which field matches the field WBS Element in the structure 'ORDER_ITEMS_IN' which is returned from the said BAPI.
Thanks in advance,
RG

Hi
In VBAP there is a field for this WBS ELEMENT PS_PSP_PNR
check for that in BAPI structures
check the field ASSORT_MOD of BAPIITEMIN .
Reward points if useful
Regards
Anji

Sale order - Wbs element Report

Hi
Is there any report for sale order wise wbs element report.
In my sale order i will give wbs element and now i want to check "for one sale order , what are the wbs elements"

You can check the WBS for a sales order from the table view of VBAP.
The WBS field is PS_PSP_PNR.
Goto SE16 and give VBAP.
Enter your sales order number and execute. Look for your WBS elements in foeld PS_PSP_PNR for the different line items.
You can also create a quick SAP query on this.

Return Order Credit Memo updation in WBS element

Hi,
I have an issue on the automatic updation of return order for WBS element, once the sales order is been assigned to the wbs and billing is done payment also made by the customer and wen the customer sends the return order stating that in those goods he wont require some goods than in sales cycle credit memo is done for the payment return to customer but is there any place where the wbs gets updated for the revenues deduction of the payment given back to customer where its has to be deducted................how to do this
Kindly help me doing this.
Thanks and Regards
Praveen B M

Hello,
Thanks for you reply and i just want to know that.
If we assign the return order to the WBS element, the credit memo automatically has the WBS element assigned to it or do we have to manually assign the credit memo to a WBS element? if yes how?
Thanks and Regards
Praveen B M

WBS element is not getting populated in Excise entry in Project billing

Hi SAP Guru's
We have the case where we are doing the billing from manufacturing plant against Project. While billing WBS element is appearing in the invoice but in excise invoice entry same is not getting populated. This is affecting RR and P&L.
Can you help me by providing the standard solution to meet this requirement or update if we can meet this requirement by some function module or through any exit.
Thanks
Surender Gupta

Hi,
In transaction" VTFA" and for your sales and billing type,select your item category and in the same scree,your pricing type should be "D".This will copy all the conditions from sales order item.
Reward if this helps.
Regards
Karan

Vendor Payments Report with WBS Elements

Dear Expert,
I am looking a report for Vendor outgoing payment against WBS Elements.
Is there any Vendor Payments report with WBS Elements in SAP? I have seen FBL1N but WBS Elements field is blank.
Thanks
Samiee.

Hi,
You mentioned WBS Element is blank; so please check in any one sample payment documnet whetehr WBS is maintained and if yes find which field it is populated. For eg; sometimes people populate this information in the text or assignment field. If that is the case then change the layout accordingly in FBL1N.
Regards
Sreekanth

Settlement of WBS element down payments to an asset under constructions

The down payment (of the transactions tcode F-47 and tcode F-110), are
always settlement wbs element (tcode CJ88), we do not want to post down
payments to the receiving asset under construction (transaction type
180 or 181).
In the down payments are always taken into account in the settlement to
an asset. The settlement of the down payment is the actual reason for
the previous update of down payments in FI (Transaction type group
15). Furthermore, the settlement of down payments to assets should
not be capitalize.

When you search on this forum try to put Date range "ALL" to get more results. Please read below threads and you will get the solution.
MIRO:Transaction in area 15 contradicts the net book value rule
Transaction in area 01 contradicts the NBV
Looks like you have a negative balance in your WBS which you are trying to settle to FA.

WBS element in VA01

Similar Messages

Maybe you are looking for