Automatic Creation of Proj def & Network Activity while cration sales order

Dear All,
I want to know how system creates project order after creating sales order.
Where is the link.
I have used std. sap data (IDEAS)
Sales Order Type PS1
Sales Area 1000/10/00
Sold 2 party 1600
Material E-1001
Company Code 1100.
I have created sales order and then releasing proj in t-code CJ2B.
And confirming the activity.
I would like to know how system automatically creates Proj def. and Network.
Regards,
Sainath

Refer below link..
https://www.sdn.sap.com/irj/scn/wiki?path=/display/plm/assembly%252bprocessing%252bwith%252bsap%252bps
Check "Assembly Processing in the Project System" in below link...
http://help.sap.com/saphelp_47x200/helpdata/en/d7/b8853488601e33e10000009b38f83b/frameset.htm
Edited by: VenkatSrinvas Konda on Feb 24, 2009 1:22 PM

Similar Messages

Automatic creation of settlement rule while creating sales order

Hi Friends,
Can any one help me how to create settlement rule automatically while creating sales order i.e saving sales order. Is there any function module or any badi which can be used.. please suggest.
thanks
bobby

Hi,
Here is the solution , First Create a sustitution by going into OPSN Transaction , only user exit say 'U902'
and write the form routine in Program named 'ZRGGBS000'
The code is below ,
*& Form U902
 Automatic Generation of Settlement Rule For WBS and Company 4180
FORM u902.
Exit For Automatic Settlement Rule Creation for WBS Billing elements
IF sy-tcode = 'CJ20N' or sy-tcode = 'CJ01' or sy-tcode = 'CJ02'.
 DATA lv_proj TYPE ps_pspid.
 lv_proj = proj-pspid.
 EXPORT lv_proj TO MEMORY ID 'PSPID'.
Calling YGPS_CJB1EXEC Program For Creating Settlement Rule
 SUBMIT ygps_cjb1exec AND RETURN.
ENDIF.
ENDFORM. "u902
*& Program YGPS_CJB1EXEC
PROGRAM ygps_cjb1exec.
 Automatic Generation of Settlement Rule For WBS and Company 4180
Called From Exit For Automatic Settlement Rule Creation for WBS Billing elements
DATA: bdcdata_wa TYPE bdcdata,
 bdcdata_tab TYPE TABLE OF bdcdata,
 itab TYPE TABLE OF bdcmsgcoll.
DATA :lv_currm LIKE bkpf-monat,
 lv_curry LIKE bkpf-gjahr,
 lv_prevm LIKE bkpf-monat,
 lv_prevy LIKE bkpf-gjahr,
 lv_proj TYPE ps_pspid,
 lv_mode TYPE c,
 lv_time TYPE sy-uzeit.
DATA :g_datfm LIKE usr01-datfm,
 g_dd(2) TYPE c, " Day
 g_mm(2) TYPE c, " Month
 g_yyyy(4) TYPE c, " Year
 g_sydatum(10) TYPE c.
IMPORT lv_proj FROM MEMORY ID 'PSPID'.
lv_mode = 'N'.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'PRZB-VARIANT'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'PRZB-VARIANT'.
bdcdata_wa-fval = 'ZGPS0001'.
APPEND bdcdata_wa TO bdcdata_tab.
CALL FUNCTION 'GET_CURRENT_YEAR'
EXPORTING
 bukrs = '4180'
IMPORTING
 currm = lv_currm
 curry = lv_curry
 prevm = lv_prevm
 prevy = lv_prevy.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-FROM'.
bdcdata_wa-fval = lv_currm.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-GJAHR'.
bdcdata_wa-fval = lv_curry.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VARC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'RKPSEL00'.
bdcdata_wa-dynpro = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_CURSOR'.
bdcdata_wa-fval = 'CN_PROJN-LOW'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PROJN-LOW'.
bdcdata_wa-fval = lv_proj.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_PSPNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_NETNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_ACTVT-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'CN_MATNR-LOW'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '/00'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=SAVE'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=VBAC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLSPO1'.
bdcdata_wa-dynpro = '0100'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=YES'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKAZB'.
bdcdata_wa-dynpro = '1000'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-BATCH'.
bdcdata_wa-fval = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'RKAUF-TEST'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=RUN'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-program = 'SAPLKABA'.
bdcdata_wa-dynpro = '0210'.
bdcdata_wa-dynbegin = 'X'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-JNAME'.
bdcdata_wa-fval = 'CJB1_EXEC'.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_SUBSCR'.
bdcdata_wa-fval = 'SAPLKABA'.
APPEND bdcdata_wa TO bdcdata_tab.
Extract the date format from the user settings
PERFORM f_get_dateformat CHANGING g_datfm.
Changing the current date format to User Profile Date Settings
PERFORM f_format_date USING g_datfm
 sy-datum+4(2)
 sy-datum+6(2)
 sy-datum+0(4)
 CHANGING g_sydatum.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STDAY'.
bdcdata_wa-fval = g_sydatum.
APPEND bdcdata_wa TO bdcdata_tab.
lv_time = sy-uzeit + 30.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-STTME'.
bdcdata_wa-fval = lv_time.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'KABA01-PRIKZ'.
bdcdata_wa-fval = space.
APPEND bdcdata_wa TO bdcdata_tab.
CLEAR bdcdata_wa.
bdcdata_wa-fnam = 'BDC_OKCODE'.
bdcdata_wa-fval = '=TAKE'.
APPEND bdcdata_wa TO bdcdata_tab.
Calling Transaction 'CJB1' for creating settlement rule
CALL TRANSACTION 'CJB1' USING bdcdata_tab MODE lv_mode .
IF sy-subrc = 0.
ENDIF.
*& Form F_GET_DATEFORMAT
 This subroutine returns the date format in the user setttigs
 <--P_G_DATFM Date Format
FORM f_get_dateformat CHANGING p_g_datfm. "#EC *
SELECT SINGLE datfm FROM usr01 INTO p_g_datfm
WHERE bname = sy-uname.
ENDFORM. " F_GET_DATEFORMAT
*& Form F_FORMAT_DATE
 This subroutine returns the date as per the user settings
 -->P_G_DATFM Date Format
 -->P_G_MM Month
 -->P_G_DD Day
 -->P_G_YYYY Year
 <--P_G_DATE Date
FORM f_format_date USING p_g_datfm
 p_g_mm
 p_g_dd
 p_g_yyyy
 CHANGING p_g_date. "#EC *
CONSTANTS: c_dot VALUE '.',
 c_slash VALUE '/',
 c_dash VALUE '-',
 c_1 VALUE '1',
 c_2 VALUE '2',
 c_3 VALUE '3',
 c_4 VALUE '4',
 c_5 VALUE '5',
 c_6 VALUE '6'.
DATA: l_day(2),
 l_month(2).
l_day = p_g_dd.
l_month = p_g_mm.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = l_month
 IMPORTING
 output = l_month.
CALL FUNCTION 'CONVERSION_EXIT_ALPHA_INPUT'
 EXPORTING
 input = l_day
 IMPORTING
 output = l_day.
CASE p_g_datfm.
 WHEN c_1.
 CONCATENATE l_day l_month p_g_yyyy INTO p_g_date
 SEPARATED BY c_dot.
 WHEN c_2.
 CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
 SEPARATED BY c_slash.
 WHEN c_3.
 CONCATENATE l_month l_day p_g_yyyy INTO p_g_date
 SEPARATED BY c_dash.
 WHEN c_4.
 CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
 SEPARATED BY c_dot.
 WHEN c_5.
 CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
 SEPARATED BY c_slash.
 WHEN c_6.
 CONCATENATE p_g_yyyy l_month l_day INTO p_g_date
 SEPARATED BY c_dash.
ENDCASE.
ENDFORM. " F_FORMAT_DATE
thanks
bobby

Error while raising sales order

Hi all,
I have created a make-to-order material with item category group and general item cetegory group 0001.
While raising sales order for that material (make-to-order) item category TAK.
I got a error stating that plant is not assigned to controlling area.
can anyone help me out in this regards.

hi pavan,
pl check this on settlement rule :
The settlement rule consists of the sender and the settlement distribution rule which includes the settlement receiving accounts, distribution factor, settlement type, and validity period. You can change the settlement rule manually.
There are two possibilities for settling sales orders. You can either:
Settle to a business segment
In this case, the settlement rule is determined automatically. You can only use this method of settlement if CO-PA is activated.
Settle to a general ledger account
In this case, you enter the settlement rule and the general ledger account number manually in the sales order.
To change the settlement rule, choose Edit ® Settlement rule.
For more detailed information about settlements and especially about processing settlement rules, see the CO Cost Object Controlling documentation.
Please consult your FI guy so that he can help you configure a settlement profile.
regards
sadhu kishore

Error determining posting period(infostructure S008,Variant Z2,RC3) while creating Sales orders from Inbound IDOCS

Hello,
I am getting this Error message"error determining posting period(infostructure S008,Variant Z2,RC3)" while creating Sales order from Inbound Idocs in the IDOC,which is affecting sales order creation.
While viewing this Info structure S008, I could see no records have been maintained. Wanted to know the reasons behind this Hard error?
Is it something related to Date Field used in the Update Rules for this Infostructure which is causing this posting period error?
Appreciate your inputs on this.
Thanks and Regards
Mohammed Roshan

Thank you Jelena,I checked the Ship. Delivery dates in the IDOC which are for Current Fiscal Year- 20140703 and 20140711,Could there be any other reason for this error?
Could it be an issue with e Update rule in this Infostructire S008
Secondly when we try change the update rule thru MC25 for this Infostructure S008,It gives a message"
"Maintenance of SAP standard updates not allowed"
Kindly advice
Thanks and Regards
Mohammed Roshan

Error while saving sales order

Hi I am encountering below error message while saving sales order:
Warehouse
Specify export data in material master
Then I go to material master to check foreign trade export tab, and I had maintained commodity code export group, country of origin and region of origin, what did I miss? Help.

Hi,
Check whether you have activated legal control data for the Sales Order type configuration in Foreign Trade.
If the Order type is activated then the following error message can pop up unless you maintain in material master.
See whether export legal control data is activated or not for the order type.
In IMG Sales and Distribution>Foreign trade>Legal control section
Regards,
Saju.S

Error throwing while creating sales order

Dear all,
While on sales order creation,We have entered order type,sales organization,distribution channel,divison,
on entering sold to party,presssing enter,error is throwing as
No customer master record exists for sold-to party
actually customer master record is already created,
We need to extend the sales area then only system is allowing to create sales order,
Is there is any setting missing in configuration ?
Thanks
Jeyakanthan

hi,
can be done in two ways
1, only for the paticular customer
goto XD01 and extend the customer by entering new sales area above
and the already exisisting sales area in the reference
2,common distribution channel and common division(this is for all the customer created in that particular sales area)
IMG>sales and distribution>master data
regards
senya

Automatic price update if key field values changed in sales order and bill

Hi Experts,
I have requirement as follows.
Scenario: - We wanted carryout the pricing based on Incoterms, customer and material. I have created the condition table with these fields. And maintained the condition record. The values will flow to sales order without any problem.

Problem: - When we change the incoterms say for CIF to FOB the system should redetermine the price automatically, but this is not happening (If will redetermine only freight). If we carryout new pricing manually the right price will flow.

Expectations: - Is their any exit or any configuration setting where in system will redetermine the price automatically if we change the field value in sales order(For the field value it will be used to create condition table).
If anyone done this please help me with setting or Exit and code to enable us to come out from the situation.
We need this to happen while creating sales order as well as billing, Since @ billing prices will be redetermined.
Thanks in advance for the needful.
With regards,
Manjunatha H.S.
M: 9740433511


Hi Shivakumar,
You can use USEREXIT_NEW_PRICING_VBAP in include SAPMV45A for this.
Regards
Nikhilesh

How to manual maintain TAX condition value while creating sales order

Hi
I am creating one Tax condition suppose JLST without access sequence .
while creating sales order I am manually maintain the % value of TAX. suppose it is 1%
then I see It show some value in TAX .
save that sales order & creating delivery document for that but when I create Invoice its show error.
" Tax code in procedure CMTAXP is invalid ".
I know the configuration only for Tax condition with vk11 condition record .
BUT now I want to maintain TAX condition at the time of creating sales order.
so I remove the access sequence of that condition .
but It shows tax code error while billing.
My main question is that If i maintain condition record while creating sales order then how i can assign Tax code .
Can it is possible ?
if yes then How?
please help me.
thank you

Hi,
The "straight-forward" answer for Tax Code creation is contact the FI consultant. He shall help you, by creating Tax codes.
I have tested, with creating a tax cond type (copy of MWST) & manually entering values. I can create Sorder, Dlv and Bill but I cannot create an Accounting document. That is because of every line (amount) a Tax code is necessary.
I THINK, you can NOT have manually filled tax codes; access sequence is needed to get the tax value (%) and the Tax code from the condition record.
There is lot of material on the web to understand Tax classification, code etc. etc. See a useful link below -
http://www.sapgeek.net/2010/04/sd-determines-tax-code/
In short Tax code is a must and take the help of your FI consultant for the configuration of the same.
BTW - Tax code is already made created for MWST, therefore I suggested that you can use MWST. Furthermore, you can change the values corresponding to Tax codes in FTXP.
But if you are a beginner in these things, better take help.

"Procurement Wizard" window opens for a particular warehouse while saving Sales Order

Hello All,
We have upgraded SAP B1 8.8 to SAP B1 9.0
My client is facing one of problem while saving Sales order using particular warehouse.
Actually client is having 4 warehouses (A,B,C,D) in which if they use one particular warehouse "A" for saving Sales order they are facing a issue. The scenario is here below:
1. Client selects all required details of sales order with along with particular warehouse "A".
2. On saving SO "Procurement Wizard" is automatically triggered even if procurement document field is unchecked in logistic tab of SO.
3. This is happening only for a particular warehouse "A". Whereas if I select other 3 warehouses (B,C,D) the system saves SO without trigerring "Procurement Wizard".
Client is using SAP B1 9.0 PL 08
We don't want this "Procurement Wizard" window to open for this. As we haven't selected any check box for "Procurement Wizard" so it should not open for a particular warehouse "A".
Do you think any issue with my warehouse or system settings? Please let me know.
Please refer screen shots.
Thanks in advance.

Hi Saurabh,
As per your Screen Shot, I think you have Add-on.
Please stop that Add-on and then check above Scenario.
Thanks
Regards::::
Atul Chakraborty

To avoid Duplicate material entry while making sales order by VA01

Sir / Madam,
While making sales order by VA01 , duplicate material also accepted by system .There should be no duplicate material in sales order list.
please suggest solution.
Thanks.

Hi,
You should use userexit USEREXIT_SAVE_DOCUMENT_PREPARE in MV45AFZZ and not USEREXIT_SAVE_DOCUMENT,.The reason behind this is prepare userexit is activated just before saving the document,so at the time of saving if the logic which you will give is not satisfied then you can set warning or error in the code.
Rewards points if useful.
Regads,
Amrish Purohit
Message was edited by:
AMRISH PUROHIT

Statistics Currency Error while posting Sales Order (No: V1453)

Hi Sappers,
I am in process of making a company in SAP ERP SD - IDES, and while posting Sales Order, after I input Sold to Party, PO no, Del Plant and Incoterms and I press ENTER: The error comes up as:
Statistics: The currency from in INR for date 25.11.2011 could not be determined.
Kindly suggest a possible solution.
Thanks
Rahul Tikku

Hi,
Just go to "OBD2", select the Accounts group of your customer and "Double Click" on it, then "Double cliick" on "Sales Data" > Further goto, "Sales" and check if "Currency" field is suppressed. if so then change it to required or optional Entry. save and update you customer master in XD02. Then try your process.
Reagrds
DSR

How to restrict the order reason in Tcode Va01 while creating sales order

Hi Gurus,
My requirement is
while creating sales order in VA01
if order type is Zvol
than the list of order reasons has to be restricted.
Now 15 are coming from OVAU tcode
I need only 5 from these.
Thanks & Reagrds
kals.

Hi,
By doing the user exit in IW32 we achieved the requirement of restriction of maintenance order TECO functionality if any Service Entry sheet pending with reference of maintneance order.
regards
JKM

How to bring in the Open Sales Orders while performing Sales Order Conv

Hi,
Could you give some suggestions on the below:
How to bring in the Open Sales Orders while performing Sales Order Conversion in R12.
Thanks
Pravin

See http://ramugvs.wordpress.com/2011/08/27/how-to-stage-and-import-an-order-using-order-import-api-apps-wms-ebiz-11i-r12/
Sandeep Gandhi

Error while creating sales order

while creating sales order for a particular plant there is error coming
NO NUMBER RANGE FOR DOC TYPE ZOS1VXBAK-AUARTSILD
PLANTXVBAK-VKBUR.
Intailly I have check the no series we have internal no series for all plant,the
number series which start 195000001, only one plant the giving the above error, rest all plant it is as applicable above series.
kindly guide me for the same.

Hi Sanjay
This is regarding number ranges defining and assigning tips which you can follow as below:
Whenever there is a new Sales Org being created, you will be required to maintain Number Ranges for Sales Documents which are allowed for your New Sales Area.
Number Ranges can be maintained Internally by the system, however it can be maintained externally also if you customize it accordingly.
In Standard SAP the Transaction code for Maintaiing Number ranges externally is VN01.
Defining - The same can be reached through in IMG as : Sales & Distribution>Sales>Sales Document Header-->Define Number Ranges for Sales Documents.
Here you provide the system a specific Number range as follows:
Number range Key Start Number range End Number Range+Current Number
For Example: If you want to propose the following Number Range
*1 9000076000 9000076999 0
The Current Number field will be kept zero as you are proposing new number range and no sales documents have been created on it , Obviously..
*1 is a Unique Two digit Alphanumeric Key, while proposing your key, you should ensure that it should not be there in the system as existing.
If you propose a key that is there in the system or if the Number Range (Start and End Series) is there in the system already, the system will throw a message that Interval already already exists. So choose a key that is unique, and which is not there in the system.
Here , by making this , you are assigning a Key to a Number Range Series.
All the symbols can be used along with numbers from 0 to 9 and Alphabets from A to Z and in any order. For example: !1, ^A, BB,Z*,M2.........
Assigning - In Assigning, you assign the particular Sales Document to the Number Range you have already proposed as above.
The Assigning Part is done as follows:
The Two digit Alpha Numeric Key is maintained or Assigned to the respective Sales Document type in V0V8.
This can also be reached in IMG by:
Sales & Distribution>Sales>Sales Document Header-->Define Sales Document Types
Locate the particular Sales Doc Type, and double click on it to display it configuration. Here you put the Two Digit Number key in the Field- "Number range External Assignment"
Besides this:
If a new Shipping Point is created then Delivery Number ranges are required to be maintained.
Similarly,
If a new Plant is created then Billing Number Ranges are required to be maintained.
Regards
Naren

Error while creating sales order with ref to contract

while creating sales order, with refernce to contract system is giving a message
Configuration not possible for material : Reason 3 --> Help
Message no. V1360
and the message is as follwed can any one explain
Diagnosis
This may have been caused by one of the following:
1. The configuration profile for the material allows or requires the bill of materials to be exploded during order processing. However, a plant has not been specified in the item.
2. The configuration profile of the material allows or requires the bill of materials to be exploded during order processing, but the order quantity in the item must be greater than 0.
3. A configuration profile has not been maintained
or
A configuration is not permitted for the material
or
4. The configuration profile of the material allows or requires the bill ofmaterials to be exploded during order processing. However, the system could not determine a date because important data is missing from the item (see incompletion log).

Hi
I think you have both Variant configuration and BOM.
Pls ensure the following.
1. BOM masterdata is maintained for the variants
2. Variant configuration is configured correctly
Configuration profile is created for the material
Knowledge base object and run time version are available
3. Maintain materials as not relevant for delivery or dont give delivery quantity as 0
Once you are sure that these are in proper shape, you can start creating order. The problem wont come.
Reward points if it helps you.

Automatic Creation of Proj def & Network Activity while cration sales order

Similar Messages

Maybe you are looking for