FM for category type of Orders

Hi All,
Please suggest the FM to retrieve the category type of the orders.
Thanks in advance.

Hi,
What exactly do you want to extract ?
there is a include which has all the order types
/SAPAPO/CONSTANTS_OM_ORDER_TYP
U can use /SAPAPO/DM_GET_CATEGORY
Cheers,
KD
Edited by: Krutiman Das on Oct 30, 2008 10:08 AM

Similar Messages

Vivado 2013.4 ERROR: [IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order

Hello,
I just downloaded and installed Vivado 2013.4 on my Xubuntu 12.04 machine. But when I try to add IP from the IP catalog, as in the ug937 Lab1 step2, it fails with obscure error messages (see below).
Here's basically what I did:
-In the Flow Navigator, i select the IP Catalog button.
-In the search field of the IP Catalog, I type DDS.
-then I double-click the DDS Compiler and my error occure.
Please Help,
Jerome.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
Analysis Results[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
set_property target_language Verilog [current_project]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
sources_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen_demo.vhd":1]
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
update_compile_order -fileset sim_1
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/fsm.vhd":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-2313] Loaded Vivado IP repository '/opt/Xilinx/Vivado/2013.4/data/ip'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-1704] No user IP repositories specified
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
Vivado Commands[Project 1-11] Changing the constrs_type of fileset 'constrs_1' to 'XDC'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
sim_1[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[HDL 9-1654] Analyzing Verilog file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sim/testbench.v":1]
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-234] Refreshing IP repositories
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-395] Problem validating against XML schema: Invalid value format for this type spirit:order
[IP_Flow 19-193] Failed to save BOM file '/home/jmassol/.Xil/Vivado-2683-ubuntu/coregen/dds_compiler_0/dds_compiler_0.xml'.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/debounce.vhd":1]
[IP_Flow 19-3378] Failed to create IP instance 'dds_compiler_0'. Error saving IP file.
[IP_Flow 19-194] Failed to save IP instance 'dds_compiler_0'.
[HDL 9-1061] Parsing VHDL file "/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd" into library work ["/home/jmassol/Desktop/Vivado/vivado_debug/ug937/project_xsim/project_xsim.srcs/sources_1/imports/ug937/sources/sinegen.vhd":1]
set_property constrs_type XDC [current_fileset -constrset]

We had the same problem when switching to Ubuntu 14.04, and there actually is a solution for it: make sure your locales are set to English.
$> env | grep LC_*
should only show english (or C) locales, all others are known to cause parsing errors in some numbers, usually caused by wrong string-to-float conversions (e.g. 18,29 in german is 18.29 in english). You can change the locales in the file /etc/default/localesThis is not the first time we had problems with the locale settings, Xilinx does not seem to test their software with anything else than en_US, causing obscure bugs like this one.
HTH
Philipp

Multiple output records for delivery type access order sequence

Hello,
This is a question about output delivery type for outbound deliveries.
I have created one delivery type YF and two output condition types YDL1 and assigned access sequence (by sales org/customer) and YDL2 (by shipping point) in NACE V2 shipping. I have also created their corresponding condition records: salesorg/cust and shipping point in VV21.
When I created my outbound delivery YF from sales order and saved it. System finds both output condition types. First YDL1 and then YDL2 as expected because condition records have been maintained. However, I need to change this order so that YDL2 is the default one and YDL1 is found next.
Could somebody help me how do I change this order?
Thank you in advanced.

Hello,
what do you mean with
I need to change this order so that YDL2 is the default one
When two or more output types are determined, they have the same "rank".
If you mean that you want to sort the output types to have one printed before the other one, please refer to point 3. of OSS Note 960611
https://websmp130.sap-ag.de/sap(bD1pdCZjPTAwMQ==)/bc/bsp/sno/ui_entry/entry.htm?param=69765F6D6F64653D3030312669765F7361…
Best regards,
Andrea

Regarding the 'Dispatch time' settings for output type...

Hi Experts,
May i know what 'Send with application own transaction' means when we configuring output type in SPRO for 'Dispatch time'.
Cause i knew if we set it as 'Send immediately', then this output type will be triggered upon saving the orders.
But i dont know what that item for..Could you kindly help me on this...
What it means if we set the dispatch time as 'Send with application own transaction' for delivery output..??
Thank you very much.

Hi,
If you choose 'Send with application own transaction' when maintaining condition record for output type,during order,delivery and invoice saving the output type signal is yellow,that means unless you select that output and trigerred for printing it will not goto the spool.i.e in simple words the output is for manual printing.......
Let me know if you need any clarifications on this..
Regards,
Chandra

Purchase Requisition / Order: Account Assignment Category for material type

Hi,
When creating a PR or PO for one specific material I would like the system to propose a specific account assignment Category for this material. It shouldn't allow the user to change this account assignment category.
Is it possible? How should I proceed?
Thanks in advance.
Luis.

I dont think there is any standard procedure for doing this.
My idea would be to use a user exit say EXIT_SAPLMEREQ_010 for PR and a similar exit for PO and code a Error message check for Material type and account assignment combination.
For ex : EXIT_SAPLMEREQ_010 is a exit which is called during check in a PR . SO when the user enters a combination of Material type and Acc assignment u can check for the requirements.

Reg: Default Requirement type Based on Sales Item category in Sales Order

I have a question, regrding Make to order and Make to stock .
I am using a Material that is default Make to Stock, based on customer requirement same material also used as a Make to order.
When i generate sales order perticular material default Make to stock Item category will pick up, for this Requirement type KSV is comming, If i Change Item category Make to Order, requirement type is not changing,
My query is when i change Item category i want default requirement which has assigned for item category.
Thanks and Regards,
Prasad.

Hi
Just try by removing the STRATEGY GROUP in MRP3 view of material master if you are maintaining any.
regards
Prashanth

SAP Best Practice for Document Type./Item category/Acc assignment cat.

What is the Best Practice for the document Type & Item category
I want to use NB - Item category - B & K ( Blanket PO) , D ( Service) and T( Text) .
Is sap recommends to use FO Only for the Blanket Purchase Order.
We want to use service contract (with / without service entry sheet) for all our services.
We want to buy asset for our office equipments .
Which is the best one to use NB or FO ?
Please give me any OSS notes or reference for this
Thanks
Nick

Thank you very much for your response.
I hope I can provide some clarity on how the accounting needs to be handle per FERC Regulations. The G/L balance on the utility that is selling the assets will be in the following accounts (standard accounts across all FERC Regulated Utilities):
101 - Acquisition Value for the assets
108 - Accumulated Depreciation Value for the assets
For an example, there is Debit $60,000,000 in FERC Account 101 and a credit $30,000,000 in FERC Account 108. When the purchase occurs, the net book value for the asset will be on our G/L in FERC Account 102. Once we have FERC Approval to acquire the plant assets, we will need to enter the Acquisition Value and associated Accumulated Depreciation onto our G/L to FERC Account 101 and FERC Account 108 respectively with an offset to FERC Account 102.
The method that I came up with is to purchase the NBV of the assets to a clearing account. I then set up account assignments that will track the Acquisition Value and respective Accumulated Depreciation for each asset that is being purchased. I load the respective asset values using t-code AS91 and then make an entry to the 2 respective accounts with the offset against the clearing account using t-code OASV. Once my company receives FERC approval, I will transfer the asset to new assets that has the account assignments for FERC Account 101 and FERC Account 108 using t-code ABUMN or FB01.

Transfer Order : Data for storage type search is not defined (A   )

Dear Experts ,
While trying to use the Transfer Order and trying to determine the storage type this error appears :
Data for storage type search is not defined (A   )
Message no. L3007
Diagnosis
Information on the storage type search has not been defined.
How ever , I have already configured the search and here is the Storage Type search's data in OMLY
1. Warehouse number : W10
2. Operation : A "Stock Removal"
3. Indicator :   E
4. Stock Category : Blank
5. Special Stock Category : Blank
6. Storage Location Ref :10
7. Storage Type : 10E
Please Advice
Edited by: Sap Sap on Feb 24, 2011 10:54 AM

Hello,
The storage type in which you want to place the material or pick the material from has not been defined in the storage type search sequence.
You need to define the search sequence in customization so that storage type is determined automatically when the transfer order is created;
SPRO>>Logistics Execution>>Warehouse Management>>Strategies>>Activate Storage Type Search
In this go to determine search sequence and then
for warehouse number W10, operation as stock removal 'A' and in this maintained the relevant the storage type (10E) so that it is determined automatically.
I hope this helps.
BR,
Tushar

Maintenance activity type and order type for plant maintenance order

How can i get the maintenance activity type and order type for a given plant maintenance order. Please let me know the table where i can get these two fields
In AFIH i can only get the MAT for an order number

Maintenance activity type -
AFIH - ILART
Order Category Indicator Plant Maintenance -
AFIH - AKKNZ
reward if heplful

Necessary Fields For Creation of Service PO of Order Type Relaese Order.

Dear Guru,
I have encountered an issue which i am trying to resolve...
My this requirment will seem little okward the way i am asking but i have no way...
The issue is I have to create a Service PO of Order type Release order (RO) using BAPI Function Module .BAPI_PO_CREATE1.
The service PO should be of multiple Item and services for particular line item should be multiple.
When I am creating this using ME21 or ME21N i am facing no issue.
But when i am using BAPI Function Module .BAPI_PO_CREATE1
i am getting following errors ;; The error which i am getting as below
T ID                   NUM MESSAGE
E BAPI                001 No instance of object type PurchaseOrder has been created. External reference:
E MEPO              000 Purchase order still contains faulty items
E SE                   029 Please maintain services or limits
E SE                   140 Service HIRING OF LCD: please specify unit of measure
But I am failing to findout in which field services or limits and unit of measurement have to maintain.
What are the necessary fields have to pass in Bapi import parameter and the table i am unable to findout.
Please show some way how to resolve this or give me some guideline to resolve this
Dear Moderator request your kind intervane to move this qurry into correct forum if i have asked this in wrong forum
Thanks and regards
saifur rahaman

Hi Saifur
Can you please elaborate how did you resolve the issue we are also facing same problem when we are trying to create the PO for service items through SRM it is throwing same error while creating the PO in SAP.
Email Id : [email protected]
Thank you in advance!!
Regards
Deepika

Transaction for characteristics per plant / order type

Transaction for characteristics per plant / order type
We need a new transaction for customizing feature
Characteristics per plant and order type
ZVP_PRNTCHARCON
example one screen - one dimension characteristics, other 15 operations
Thanks

Hi Tarun,
Standard SAP does not support char specific to plant & order type. You need to devlop some custom transaction. If you are looking more details, request you to share the business requiremnet, details etc.
Thanks...Sanjay

Change Item Category in Sales Order for KMAT materials

Hi,
How can I change item category in sales order/quote for KMAT materials?
Currently in the sales order/quote, the item category field is grayed out for KMAT/configurable materials and I can change the item category.
Please help me.
Sincerely.
Ketan

Dear Ketan,
I hav exactly the same problem.
Did you finally succeed?
Thanks.
Ben.

Stock transport order between storage locations and assignment category type E not in MRP

Hello Gurus,
I have a stock transport order between 2 storage location which belongs to the same plant. Besides the stock transport order is allocated to a sales order (account assigment category E). When I run the MD03, the system take into account the quantity of the stock transport order as a future entry and this is wrong. I need that the MRP has not into account the stock transport order as an entry.
As an important information, If I modify the stock transport order removing the account asignment category E (sales order), then the MRP doesn't take into account it, so this is correct.
Could anybody tell me how to get it?
Thanks in advanced.

Laura,
It is normal that MRP will consider an STO as a receipt element; this is basic planning. It is unclear to me why you think you do not want it to do so, but I will assume you have some logical reason.
Contrary to what some others may have suggested, changing the scope of check for availability checking has no effect on which elements are considered for MRP. MRP is a completely separate functionality from Availability Check.
For Location > Location STOs (within a plant), then, you normally have the receipt element of the STO in the destination storage location, and the requirements element of an equal amount in the source storage location. Net of these two elements is zero, unless you have already issued the STO at the source location.
Changing the Account assignment from "E" means that the STO will not be relevant for your Sales order (in other words, when you receive this STO into the destination storage location, it cannot be used for your sales order). In a general MTO scenario, it also means that the proceeds of this STO (the stock you received) cannot be used for ANY sales orders.
One way that some people make an STO 'not relevant' for MRP is to alter the destination storage location such that it is not relevant for MRP. You can change the MRP relevancy of the storage location in MM02 > MRP4 tab
Best Regards,
DB49

Settings for costing data in order types for plant maintenance

i want to know the purpose of settings for costing data in order types for plant maintenance. do we need to do it for sure i mean are those settings mandatory to analyze the costs on work order

Yes you need to maintain those settings, as the plant maintenance orders are also considered as cost objects and in order for you to post any cost, you need to have a cost object. Unless you maintain these settings, the cost you posted cannot be settled to a cost center.
Assign points as a way to say thanks.
Madhav Nanduri

How to create a Inbound delivery type for a special purchase order type

Hi,
I try to create a special Inbound delivery type for a special purchase order type (a transfer purchase order).
In SD module, I can créate a special outbound delivery and precise the sale order type, but I don't manage to do it for a Inbound delivery type.
Do you know if i can do it without specifiq?
Regards,
Roselyne

Hi Roselyne,
What you experienced is standard system behavior. Inbound delivery type is uniquely assigned to confirmation control key. You can only specify confirmation control key on item level in PO. The assignment of Delivery type can be seen in the following table:
T163D
IBTYP EBTYP LFART RETDLV
1        AB                      X
2        LA        EL           X
3        GW       EG
The field T163D-IBTYP is checked in different programms. For example in programm RM06ENAB (TA: ME92F). If you insist to customize the determination of delivery type by PO type, I strongly suggest you discuss with the Application consultants before making the modifications to ensure it won't impact other areas.

FM for category type of Orders

Similar Messages

Maybe you are looking for