WBS element determination in SD billing

Hi All,
We are using WBS element for positing accounting document in billing.
In our case flow starts from Service order->QT -> debit memo req-> Debit memo.
WBS element is mandatory field in Service order(IW31) and with reference to Service order DMR is created.
While creating the Debit memo in VF01 different WBS element is getting determined which is not activated for account postiing in CJ03.
Kindly help me out why the different WBS element is coming in billing doc and how this determation will happen in billing.
Regards,
Shameel

Hi Shameel,
how are you assigning WBS element in Service Order, is it from the project or just randomly you are assigning ?
try to find if any substitution rule assigned to the WBS in CJ20N transaction
Also why you need Account assignment posting to WBS as Debit memo request is created with Service Order, you can settle to the Service order
Let me know what you are trying to do
thanks
santosh

Similar Messages

WBS element- Sales Order

Dear Gurus,
In WBS element If dont tick on Billig element system will not allow assign this WBS element while creating a Sales Order.
How it is happening,where can i find out these settings.
Cheers,
Sumith

Hi
Is it really a standard SAP behaviour which will allows only billing WBS element to be account assigned to a sales order line item? There must be some setting in sales item category or document type or requirement class. Anybody has any idea?
All of a sudden in my case the sales order document is behaving differently. It is also accepting a non-billing WBS element to be account assigned.
Some document says that even a non-blling (operative indicator) WBS element can be account assigned. However revenues can flow from sales order only if the WBS element is ticked as billing element.
In that case, how to set a control in the sales document from not accepting a non-bllling WBS element to be account assigned?
Regards
Srikrishna

Downpayment..milestone..periodic billing...WBS element...

downpayment..milestone billing.....periodic billing...WBS element...billing plan..commission agent....rentals...extra work in construction...cancellation of flat..allotment of parking..sale of real estate unit..sale of TDR..sale of services...payment terms..
these are the words making me MAD for the last few days can anyone have an idea on real estate business..how it actually works in SAP. i mean to say that how in SAP SD we work on the standard system with out using SAP RE-FX module...
and as in a part of business process after the creation of order wat we actually do..whether delivery or billing process.. and how the collection part from the customer will come in to picture..
the answer will send me from SUN to MOON...
thanx

Hi Nagendra Prasad,
Please find good stuff on Billing Plans Below:
1. Resource Related Billing
Configuration at Broad level will be as under:
1. Configuration of Project System to create Projects. (PS)
2. Sales Order Type as Main Order (SD)
3. Configuration for Hours maintainance (PS)
4. Sales Order Type for Dependend Order (SD). This order should be having control as automatic. It will be taken automatically in Billing Request through DIP Profile.
5. DIP Profile (PS / SD)
6. Billing Type (SD)
7. VKOA setting for G/L account Determination (SD / FI)
2. Milestone Billing
This can be configured using Milestone Billing.
1. Create New Sales Order Type, say ZOR (Copy of OR) through T.Code: VOV8
Maintain Delivery Type as LF & Billing Type As 'F1' - Order Related / 'F2' Delivery Related.
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Documents Types
2. Assign New Sales Document Type to Sales Area, For Eg:
1000 (S.Org) / 10 (D.Channel) / 10 (Division) / ZOR (S.O Type)
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Assign Sales Area to Sales Document Type
3. Create New Item Category, say ZTAN - Copy of TAN (For delivery Related) / ZTAD - Copy of TAD (For Order realted) / ZTAS - copy of TAS (For Third Party)
Maintain as under (others remaining same)
Billing Relevance: I
Billing Plan Type: 01
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Define Item Category
4. Assign Item Category, for ex (assuming Usage & higher level item category as blank):
Sales Document Type | Item Category Group | Default Item Category
ZOR | NORM | ZTAN
ZOR | DEIN | ZTAD
ZOR | BANS | ZTAS
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Assign Item Category
Note: In the above Billing Type '01' plays the main controller for milestone billing. In Sales order, at item level, we require to maintain the billing plan.
Follow the Sales cycle as normal sales cycle for particular Scenarios
3. Periodic Billing
This can be configured using Periodic Billing.
1. Create New Sales Order Type, say ZOR (Copy of OR) through T.Code: VOV8
Maintain Delivery Type as LF & Billing Type As 'F1' - Order Related / 'F2' Delivery Related.
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Define Sales Documents Types
2. Assign New Sales Document Type to Sales Area, For Eg:
1000 (S.Org) / 10 (D.Channel) / 10 (Division) / ZOR (S.O Type)
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Header > Assign Sales Area to Sales Document Type
3. Create New Item Category, say ZTAN - Copy of TAN (For delivery Related) / ZTAD - Copy of TAD (For Order realted) / ZTAS - copy of TAS (For Third Party)
Maintain as under (others remaining same)
Billing Relevance: I
Billing Plan Type: 02
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Define Item Category
4. Assign Item Category, for ex (assuming Usage & higher level item category as blank):
Sales Document Type | Item Category Group | Default Item Category
ZOR | NORM | ZTAN
ZOR | DEIN | ZTAD
ZOR | BANS | ZTAS
IMG > Sales and Distribution > Sales > Sales Documents > Sales Document Item > Assign Item Category
Note: In the above Billing Type '02' plays the main controller for periodic billing. In Sales order, at item level, we require to maintain the billing plan
Have a look to these SAP documents: very useful they explain all.
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/MYSAP/SR_CS.pdf
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/CS/PMSMASC.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/31/03953401024735e10000009b38f83b/frameset.htm
Please Reward If Really Helpful,
Thanks and Regards,
Sateesh.Kandula

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

Automatic determination of WBS element in MIGO

Dear Friends,
I have a requirement as below:
When we do reservation for a particular WBS element and do goods issue for a different WBS element, system is not giving any error message.
We want to configure automatic determination of WBS element in MIGO_GI from Reservation and the WBS field should be disabled for editing while doing Goods Issue. Please suggest on the required configurations.
Regards,
Deepa

I'm totally agree with Pete.
This info can accelerate search and development
IQSM0007 Customer exit for goods movements
This customer exit is used to transfer the document data for a goods movement into serial number management. This involves:
The complete goods document (transfer table S7_TAB_MSEG, structure MSEG),
The purchase order history (transfer table S7_TAB_EKBE, structure EKBE).
The customer exit is called as soon as the document is saved. This means that at this moment in time the document data can be placed in the global memory of function group XQSM, where it is then available when the serial numbers in the document are saved immediately afterwards.
Access to the document data (placed in the global memory of IE01) is performed in customer exit EXIT_SAPLIE01_005, which can be activated using customer exit IQSM0005.
Certain document data can now be copied into the master data of the serial numbers.
Example
You want to copy the goods recipient from the material document and the value from the purchase order history into the serial number.
Goods movement
You activate the customer exit EXIT_SAPLIE01_007 so that you can prepare the required information from the goods document and the purchase order history. You can read additional data (for example, from the purchase order) where necessary.
Posting
You activate the customer exit EXIT_SAPLIE01_005. The data prepared with user exit EXIT_SAPLIE01_007 is available here (for example, goods recipient or purchase order value). This data can be copied into the master data of the serial numbers.

WBS Element ( Billing element ) assignment at sales order header level

HI,
There is provision of assign WBS Element at sales order header as well as item level , If Project WBS Element is assigned for each line item delivery and stock updating is happening from the project, But WBSE will assign at sales order Header system will not allowing to create project delivery( moment type 601Q), and stock updation ftom project.
Please let me know how this will happen ,
Regards,
Gangi
Edited by: Gangi Reddy Botchu on Jul 7, 2008 4:50 PM

SPRO - SD - Billing - Billing Plan - the first 5 config nodes (Define Billing Plan types / Define Date descriptions / Assign Date categories / Maintain Date Proposals / Assign Billing Plan types to Sales Doc types) are applicable to you.
this is pretty tranparent for a reference.
What else is required?

Getting Billing Element in Purchase Order Using WBS element.

Hi,
What is the process and logic to get the billing element and the corresponding Sales order details using the WBS element or network of the account assignment category in the Purchase order line item.Please suggest the tables to be used to fetch the Sales order details using this procedure.
Thanks
Anand

Project PO can be generated in following methods.
1.When a Material attached to Activity in the Project, PR can be generated with A/C assignement Q. System wil copy the WBS element to which activity is assigned in the account assignment tab of PR. When PO is created with reference to PR, system wil automatically copy the WBS from the PR in to PO account assignment tab.
2. U can directly create PO with account assignment Q and assign WBS in account assignment tab.

WBS element field in SO for milestone billing

Hi,
I am using Milestone billing. When I am trying to create the Sales order the WBS element field is greyed out. Pleae advise.
Regards,
Santanu

Hi Shantanu,
I think you need to remove the assignment of the requirement type KE from your item category. I gues you are using TAO as the item category for Milestone.
You go to Sales and DistributionBasic FunctionsAvailability Check and Transfer of RequirementsTransfer of RequirementsDetermination Of Requirement Types Using Transaction.
Hope it helps.
Shivaji.
Edited by: Shivaji Paul Choudhury on Mar 2, 2009 4:21 PM

WBS element withot Billing element

Hi Is it possible to create sales order with account assinment ' WBS element w/o Billing element' ?

Not possible to my knowledge.
But what is your scenario?
Regards
Sreenivas

Billing of a WBS Elements when we use a purchase order.

Hi,
My question is: Usually we use purchase order of the provider to create the delivery and after that the billing document. We use transaction VL04 to do that. It is a process of intercompany billing.
We have too, a process that we use a WBS Elements and after that we create a delivery and a billing document.
So, how can i use the two billing process in the same bill? The goal would be bill a WBS Elements using the original purchasing order of the provider VL04.
           Best Regards
              João Fernandes

Hi,
My question is: Usually we use purchase order of the provider to create the delivery and after that the billing document. We use transaction VL04 to do that. It is a process of intercompany billing.
We have too, a process that we use a WBS Elements and after that we create a delivery and a billing document.
So, how can i use the two billing process in the same bill? The goal would be bill a WBS Elements using the original purchasing order of the provider VL04.
           Best Regards
              João Fernandes

Billing Level WBS element

Hi,
Iam Running a report.   If i key in Project # and weekend dates , The Report Should fetch WBS element, WBS element - Billing Level , etc etc
Suppose a project 13381 has wbs elements 13381.001, 13381.101, 13381.501. The WBS Element Billing level for them are 13381-B01, 13381-B02, 13381-B03.
This is coming Properly in the Report.
But When I Key In Project Number as Select-options.
   Project #    13381   to 13382
Iam Not Getting The Billing level of 13382 , But Iam properly getting The billing level for 13381.   If the execute the report with single Project I get it properly , But The same thing with range   Iam not getting Billing level for the Other Projects in the Range.
Below is the Code only for Fetching WBS level 2 .
Plz Tell me , How do i get the billing level for the all the projects in Range. What should i change in the code
   DATA: TEMP_PSPNR    LIKE PRPS-PSPNR.
DATA: BEGIN OF INT_PRHI OCCURS 0,
          LEVEL(1)    TYPE C,     "level in the hierarchy
          WBS         LIKE PRHI, "Record for hierarchy
        END OF INT_PRHI.
DATA: LEVEL2_INIT(1)     TYPE C. "set to initial for each new proj
DATA: BEGIN OF LEVEL2_PRPS OCCURS 0,
          POSNR       LIKE PRHI-POSNR,
          POSID       LIKE PRPS-POSID,
          POST1       LIKE PRPS-POST1,
   END OF LEVEL2_PRPS.
IF PRPS-PSPNR <> TEMP_PSPNR.
    MOVE PRPS-PSPNR TO TEMP_PSPNR.
    MOVE PRPS-POSID TO ITAB-X_WBSELEMENT.
ENDIF.
PERFORM FIND_LEVEL_2
            USING      PROJ-PSPNR
                       TEMP_PSPNR.
ITAB-X_WBS_LEVEL2TITLE = LEVEL2_PRPS-POST1.
ITAB-X_WBS_LEVEL2 = LEVEL2_PRPS-POSID.
FORM FIND_LEVEL_2
    USING     PROJECT
              WBS.
DATA: TOP_POSNR    LIKE PRHI-POSNR,
        FIND_POSNR   LIKE PRHI-POSNR,
        SECOND_POSNR LIKE PRHI-POSNR.
IF LEVEL2_INIT IS INITIAL.
    LEVEL2_INIT = 'X'.
    CLEAR INT_PRHI.
    REFRESH INT_PRHI.
    SELECT * FROM PRHI
          WHERE PSPHI = PROJECT.
      MOVE-CORRESPONDING PRHI TO INT_PRHI-WBS.
      APPEND INT_PRHI.
    ENDSELECT.
    SORT INT_PRHI BY WBS-POSNR.
    LOOP AT INT_PRHI WHERE WBS-UP = '00000000'.
      EXIT.
    ENDLOOP.
    TOP_POSNR = INT_PRHI-WBS-POSNR.
    LOOP AT INT_PRHI WHERE
          WBS-UP = TOP_POSNR.
      INT_PRHI-LEVEL = '2'.
      MODIFY INT_PRHI.
      SECOND_POSNR = INT_PRHI-WBS-POSNR.
      LOOP AT INT_PRHI WHERE
            WBS-UP = SECOND_POSNR.
        INT_PRHI-LEVEL = '3'.
        MODIFY INT_PRHI.
      ENDLOOP.
    ENDLOOP.
ENDIF.
FIND_POSNR = WBS.
DO 10 TIMES.
    LOOP AT INT_PRHI
        WHERE WBS-POSNR = FIND_POSNR.
          ENDLOOP.
    IF INT_PRHI-LEVEL = '2'.
      SECOND_POSNR = INT_PRHI-WBS-UP.
      SELECT SINGLE * FROM PRPS WHERE PSPNR = FIND_POSNR.
          SELECT SINGLE * FROM PRPS WHERE PSPNR = SECOND_POSNR.
      LEVEL2_PRPS-POST1 = PRPS-POST1.
      LEVEL2_PRPS-POSID = PRPS-POSID.
      EXIT.
    ENDIF.
    FIND_POSNR = INT_PRHI-WBS-UP.
ENDDO.
SELECT SINGLE * FROM PRPS WHERE PSPNR = WBS. "resets prps!!!
ENDFORM.

Hey Guys,
I Corrected it Myself, the problem was in the
FORM FIND_LEVEL_2
USING PROJECT
WBS.
<b>IF LEVEL2_INIT IS INITIAL. ]
LEVEL2_INIT = 'X'.</b>        ]
These shud be taken off , if the Projects are in range , The above works only for a single project.

Error no WBS billing element found while substituting WBS element

Hello,
I've this error while doing an intercompany billing.
I have to companies with cross company process in CO.
I've one project with only one WBS element, and I've insert it in the purchase.
I've chequed Billing documents in the WBS element.
Any suggestion?
Thanks in advance
Emilio Roldan

Dear expert
           /thread/1505596 [original link is broken]
          Error no WBS billing element found while substituting WBS element 00050923
Regards
      Ajeesh.s

WBS element in billing

Hello...
gettting the below error that while generating InterCo. billing.
"No WBS elemant found while substituing WBS element"
but on the other hand no such error is coming while creating F2.
I donn know may be due to different Cocode.(since error is coming in IV only).
is something needs to be done at WBS element or SD side???
pls elobrate...
Thnx in Advance

for intercompany billing your WBS structure must contain a billing element at each co code hierarchy
L1 mark as billing element cocode 1
L1-1
L1 -2 mark as billing element cocode 2
L1-1-1
L1-2-1

Billing WBS element

Is thier any function module or BAPI to find whether the Particular WBS is billing element or not.
Thanks & Regards
Avijit Khajanchi

tables:
   prps.
types :
      begin of ty_prps,
        pspnr type prps-pspnr,
      end of ty_prps.
data :
     it_prps type standard table of ty_prps,
     wa_prps type ty_prps.
select-options
     s_PSPNR for PRPS-PSPNR.
Start-of-selection.
   select pspnr
             from prps
             into table it_prps
            where pspnr in s_pspnr and
                       fakkz = 'X'.
IF sy-subrc = 0.
     loop at it_prps into wa_prps.
       write : /5 wa_prps-pspnr.
    endloop.
endif.
You will get all the wbs elements which are billing.
Regards
Satish Boguda

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

WBS element determination in SD billing

Similar Messages

Maybe you are looking for