Mvmt Type 122 value different than Mvmt Type 101 value

Is it standard in SAP for the $ unit value of a 122 tx to be different than the $ unit value of a 101 tx? Can the parameters in SAP be changed for 122 tx to debit GRIR at PO price so that the 101 tx and 122 tx clear? It seems the 122 tx is values at invoice price and not PO price?

Dear,
If 122 movement value is different from 101 -
1. Check on what basis system picking the value for 122 movement. From Moving average price?
2. Let's know you are doing 122 reference to PO or original 101 document number?
Meanwhile, try with MB01 reference to PO number - 122 movement.
Regards,
Syed Hussain.

Similar Messages

Condition value of Tax condition type gets added to Total Value in Contract

Hi All,
I'm currently investigating an issue where there are 2 line items in an SAP Sales Contract. There is a human error in the second line where the billing end date is less than billing start date in the billing plan. Consequently, the second line has null Outgoing target value.
However, the header Total value in the Contract gets wrongly calculated as Basic condition value of 1st line + Condition value of tax condition type of line one due to this.   When I modify the billing end date for the second line item to be a date greater than the billing start date, the above problem disappears and the total value of the contract does not include the tax component.
For eg.
Normal Error free Contract
Total Value at Header =   700.00 EUR
                   Material          Outgoing Target val
Item 0010    MAT1               450.00                          ( 450 + 50 (tax ) )
Item 0020    MAT2               150.00
Contract with billing plan error in second line
Total value at Header =   550.00 EUR
                        MAterial       Outgoing target val
Item 0010         MAT1             450.00                    ( 450 + 50 (tax ) )
Item 0020         MAT2              0.00
Any inputs would be most welcome.
Regards,
Venkatesh.
Edited by: Venkatesh Gopalarathnam on Jan 24, 2012 9:48 AM

No, i didn't.
Actually, i enter condition type and amount in sales order manually.
At that time my program which i modified at 'Define And Assign Pricing Procedures' in IMG should be run.
But the result of running is different from my purpose.
To change Condition value of condition type in sales order, are there any solution?

Why a Constant has to be of type Static final rather than final?

Hi,
I struck up with a basic doubt
Why a Constant has to be of type Static final rather than final?
Hoping for quick reply
Venu.

Hi,
I struck up with a basic doubt
Why a Constant has to be of type Static final rather
than final?It doesn't have to be, but it usually makes more sense for it to be static (associated with the class) than non-static (associated with the instance). If every instance of the class will have the same value for that variable--whether it's final and a constant or not--it makes sense to make it static. There's no need for multiple copies of the same value. (And in the case of non-final variables, it can lead to incorrect program behavior if it's not static.) If each instance of the class could potentially have a different value for that variable, then it has to be non-static.

RTV user status - movement type 122

Hello,
We are trying to trigger RTV (Return To Vendor) user status
automatically from the movement type '122' and vice versa back to AVLB
with the reversal (movement type '123'). We tried to search for the SAP
standard business through the IMG for user status (IMG > Plant
Maintenance and Customer Service > Master Data in Plant Maintenance and
Customer Service > Basic Settings > Define User Status). The only
Business Transaction that does the automatic trigger is 'Goods Issues'.
However, we are already utilizing this 'Goods Issues' business
transaction for other user status. (ie. 'YARD'). Besides, it does not
make sense that Goods Issues will trigger RTV user status. Please
advise.
Thanks and regards,
Hendra Kosasih

Hi,
I think its not possible to assign 2 different user statuses for single document. As you are using one status already while doing goods issue, you cant assign another status simultaneously.
You try to create user fields & assign some value based on your requirement while posting the document.
regards,
Maheswaran.

Senarious for using different internal table types

please give scenarios for using different internal table types?

Refer to the following.
Internal table types
This section describes how to define internal tables locally in a program. You can also define internal tables globally as data types in the ABAP Dictionary.
Like all local data types in programs , you define internal tables using the TYPES statement. If you do not refer to an existing table type using the TYPE or LIKE addition, you can use the TYPES statement to construct a new local internal table in your program.
TYPES <t> TYPE|LIKE <tabkind> OF <linetype> [WITH <key>]
[INITIAL SIZE <n>].
After TYPE or LIKE, there is no reference to an existing data type. Instead, the type constructor occurs:
<tabkind> OF <linetype> [WITH <key>]
The type constructor defines the table type <tabkind>, the line type <linetype>, and the key <key> of the internal table <t>.
You can, if you wish, allocate an initial amount of memory to the internal table using the INITIAL SIZE addition.
Table type
You can specify the table type <tabkind> as follows:
Generic table types
INDEX TABLE
For creating a generic table type with index access.
ANY TABLE
For creating a fully-generic table type.
Data types defined using generic types can currently only be used for field symbols and for interface parameters in procedures . The generic type INDEX TABLE includes standard tables and sorted tables. These are the two table types for which index access is allowed. You cannot pass hashed tables to field symbols or interface parameters defined in this way. The generic type ANY TABLE can represent any table. You can pass tables of all three types to field symbols and interface parameters defined in this way. However, these field symbols and parameters will then only allow operations that are possible for all tables, that is, index operations are not allowed.
Fully-Specified Table Types
STANDARD TABLE or TABLE
For creating standard tables.
SORTED TABLE
For creating sorted tables.
HASHED TABLE
For creating hashed tables.
Fully-specified table types determine how the system will access the entries in the table in key operations. It uses a linear search for standard tables, a binary search for sorted tables, and a search using a hash algorithm for hashed tables.
Line type
For the line type <linetype>, you can specify:
Any data type if you are using the TYPE addition. This can be a predefined ABAP type, a local type in the program, or a data type from the ABAP Dictionary. If you specify any of the generic elementary types C, N, P, or X, any attributes that you fail to specify (field length, number of decimal places) are automatically filled with the default values. You cannot specify any other generic types.
Any data object recognized within the program at that point if you are using the LIKE addition. The line type adopts the fully-specified data type of the data object to which you refer. Except for within classes, you can still use the LIKE addition to refer to database tables and structures in the ABAP Dictionary (for compatibility reasons).
All of the lines in the internal table have the fully-specified technical attributes of the specified data type.
Key
You can specify the key <key> of an internal table as follows:
[UNIQUE|NON-UNIQUE] KEY <col1> ... <col n>
In tables with a structured line type, all of the components <coli> belong to the key as long as they are not internal tables or references, and do not contain internal tables or references. Key fields can be nested structures. The substructures are expanded component by component when you access the table using the key. The system follows the sequence of the key fields.
[UNIQUE|NON-UNIQUE] KEY TABLE LINE
If a table has an elementary line type (C, D, F, I, N, P, T, X), you can define the entire line as the key. If you try this for a table whose line type is itself a table, a syntax error occurs. If a table has a structured line type, it is possible to specify the entire line as the key. However, you should remember that this is often not suitable.
[UNIQUE|NON-UNIQUE] DEFAULT KEY
This declares the fields of the default key as the key fields. If the table has a structured line type, the default key contains all non-numeric columns of the internal table that are not and do not contain references or internal tables. If the table has an elementary line type, the default key is the entire line. The default key of an internal table whose line type is an internal table, the default key is empty.
Specifying a key is optional. If you do not specify a key, the system defines a table type with an arbitrary key. You can only use this to define the types of field symbols and the interface parameters of procedures . For exceptions, refer to Special Features of Standard Tables.
The optional additions UNIQUE or NON-UNIQUE determine whether the key is to be unique or non-unique, that is, whether the table can accept duplicate entries. If you do not specify UNIQUE or NON-UNIQUE for the key, the table type is generic in this respect. As such, it can only be used for specifying types. When you specify the table type simultaneously, you must note the following restrictions:
You cannot use the UNIQUE addition for standard tables. The system always generates the NON-UNIQUE addition automatically.
You must always specify the UNIQUE option when you create a hashed table.
Initial Memory Requirement
You can specify the initial amount of main memory assigned to an internal table object when you define the data type using the following addition:
INITIAL SIZE <n>
This size does not belong to the data type of the internal table, and does not affect the type check. You can use the above addition to reserve memory space for <n> table lines when you declare the table object.
When this initial area is full, the system makes twice as much extra space available up to a limit of 8KB. Further memory areas of 12KB each are then allocated.
You can usually leave it to the system to work out the initial memory requirement. The first time you fill the table, little memory is used. The space occupied, depending on the line width, is 16 <= <n> <= 100.
It only makes sense to specify a concrete value of <n> if you can specify a precise number of table entries when you create the table and need to allocate exactly that amount of memory (exception: Appending table lines to ranked lists). This can be particularly important for deep-structured internal tables where the inner table only has a few entries (less than 5, for example).
To avoid excessive requests for memory, large values of <n> are treated as follows: The largest possible value of <n> is 8KB divided by the length of the line. If you specify a larger value of <n>, the system calculates a new value so that n times the line width is around 12KB.
Examples
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
The program defines a table type ITAB. It is a sorted table, with line type of the structure LINE and a unique key of the component COLUMN1.
TYPES VECTOR TYPE HASHED TABLE OF I WITH UNIQUE KEY TABLE LINE.
TYPES: BEGIN OF LINE,
COLUMN1 TYPE I,
COLUMN2 TYPE I,
COLUMN3 TYPE I,
END OF LINE.
TYPES ITAB TYPE SORTED TABLE OF LINE WITH UNIQUE KEY COLUMN1.
TYPES: BEGIN OF DEEPLINE,
FIELD TYPE C,
TABLE1 TYPE VECTOR,
TABLE2 TYPE ITAB,
END OF DEEPLINE.
TYPES DEEPTABLE TYPE STANDARD TABLE OF DEEPLINE
WITH DEFAULT KEY.
The program defines a table type VECTOR with type hashed table, the elementary line type I and a unique key of the entire table line. The second table type is the same as in the previous example. The structure DEEPLINE contains the internal table as a component. The table type DEEPTABLE has the line type DEEPLINE. Therefore, the elements of this internal table are themselves internal tables. The key is the default key - in this case the column FIELD. The key is non-unique, since the table is a standard table.
http://help.sap.com/saphelp_nw04/helpdata/en/fc/eb35de358411d1829f0000e829fbfe/content.htm

Data type of the base attribute or the base value does not match...

...the assigned expression.
Hello all,
I always get the Error
+<ERROR+
TEXT="'DWH.CUB_REGISTRATIONS_AW.REGISTRATIONS': XOQ-02517: Der Datentyp des Basisattributs oder der Basisgröße stimmt nicht mit dem zugeordneten Ausdruck überein.
XOQ-01400: Ungültige Metadatenobjekte"/>
The English message must be something like this:
The data type of the base attribute or the base value does not match the assigned expression.
when I run my mapping. The attribute REGISTRATIONS is NUMERIC (12,2) in the Cube and I map a NUMERIC(12,2) constant in it.
I use a simple OWB-Mapping for loading, but I don't understand why it doesn't function. Other mappings where the attributes are out of a
table I put in a cube are running well.
I tried different things, but nothing fixed my problem. Any idea ?
Thanks a lot for help
Michael

Technically this is a 'warning' from the server, not an 'error'. This means that the change you made should have been submitted, but you get an warning message on the client. AWM would suppress this warning, but evidently OWB does not. Can you switch to use AWM?
Here is the definition of the warning along with 'cause' and 'action' sections. (Unfortunately these sections are not translated into German for some reason.)
>
02517, 0, "The data type \"%(1)s\" of the base attribute or base measure is different from the mapped expression \"%(2)s\"."
// *Cause: Either the base attribute or base measure with the mapped expression was set to an inconsistent data type, or it was mapped to an expression of a different data type from its fixed data type.
// *Action: When changing a mapped expression for a base attribute or base measure, ensure that the expression has the same data type; otherwise, set the data type of the base attribute or base measure to NULL first. When a base attribute or a base measure has an existing mapped expression, do not set it to a different data type.
>
It is probably safe to ignore this warning, but if you can post the relevant XML for the cube, then will probably be able to spot the problem. I assume that REGISTRATIONS is a measure in the cube CUB_REGISTRATIONS_AW, so this is what you can look for in the XML:
(1) The definition of the base measure along with the datatype. It should be something like this
<Measure>
<BaseMeasure
    SQLDataType="NUMBER(12,2)"
    ETMeasureColumnName="REGISTRATIONS"
    Name="REGISTRATIONS">(2) The mapping info for the measure, which should looks something like this:
<MeasureMap
Name="REGISTRATIONS"
Expression="...">
<Measure Name="REGISTRATIONS"/>
</MeasureMap>I don't know if you can get the XML directly from OWB. If not, then DBMS_CUBE.EXPORT_XML should work (assuming you are in 11.2). You could also attach AWM and save the cube to an XML template.

Movement type 122 & 161

What is the difference between Movement type 122 & 161?
Request to provide business process explanation also.
Regards,
Vengat

Hi Raghavan,
The basic diffrence between these two movemnt types is,
122: you can return material to the vendor when you know the PO number or GR number. The major advantage here for us is material get returned with same value when GR taken.
161: Returns PO, here we will retun the material by creating the PO with Returns flag.As soon as you take GR system returns the material with price given in the PO. Here system takes the price given in the Returns PO.
The business functinality of the both are, If you taken the 100 qty GR from the vendor and 80 got accepted and 20 rejected. Then it is advisable to go for 122.
But you have procured material from various vendors and 100 Gr qty only 1 pc got rejected and like that in case of other vendors. In cumulative you got some 30 pcs that are not usable. In that case you negotiate with any vendor to take that material at agreed price. In this case we go for Returns PO. Stock get returned with the agreed price.
Thanks,
Krishna Reddy

ME23N - Movement type 122

HI Guys,
i have an order xxxx with a net price of 3,29 USD. now the warehous made the movement type 122 and in purch. order history i can see it.
now the issue is, i have a different amount between local amount and amount.
for me the local amount is EUR and the Amount is USD.
it seems that doing the movement type 122 the price 3,29 was taken in EUR and not in USD, how can i check this?
any suggestion?
thanks
C.

yes.
In the PO i have a material with net Price 3,29 USD. The warehouse made mov. type 122 with mb01 to return some of this material to the vendor (50 KG). now if i go to the po history i see movement type 122 quantity 50 amount 199,09 USD as you can see the price has changed.
i cannot find any document that state that the price has changed. in the fi documents related to that movement there is already 199,09 as amount.
can this be dependent to the moving avarage price?
can you please help me?
thanks
C.

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

Error in quantity/value determination in condition type P101

Dear experts ,
I am getting bthe following message in the condition type analysis in PO for the condition type P101 . I want to know from where does the sysytem pick th value of the said condition in PO . Further , I observe that the system in NOT picking up the MAP/ SP of the material . It takes some other value . In some cases even if the MAP exists the system picks the value as "0.00 " for the said condition type in PO .
Please guide
Regards
Anis

Dear Experts ,
P101 condition type is not picking the MAP value in PO . It sometimes takes 0.00 or some other value other than MAP . Please tell me what could be wrong ?
Regards
Anis

Reason code required for movement type 122

I am getting the above error and looked up a thread on the forum which applies to my scenario. However there was a mention of defining a text schema and assigning it to the movemnt type. Can someone help me how to do that?
Jai
The thread is as follows:
We are running SRM 550 with Extended Classic scenario. When I attempt to create a return delivery, I get an error message saying: A reason has to be entered for movement type 122. But there is no way to enter the reason, i.e no fields or indicators.
<b>The text schema for return delivery is maintained and assigned to the document type for confirmations -</b> as far as I am aware this is all the config which is necessary to activate the reason for return delivery function. Am I missing something??

Hi Jai
Text Types Menu Path : SPRO -> SAP Implementation Guide → Supplier Relationship Management → SRM Server → Cross- Application Basic Settings -> Text Schema -> Define Text Types
Text Schema: Menu Path : SPRO -> SAP Implementation Guide → Supplier Relationship Management → SRM Server → Cross- Application Basic Settings -> Text Schema -> Define Text Schema
Fixed Values: Menu Path : SPRO ->SAP Implementation Guide → Supplier Relationship Management → SRM Server → Cross- Application Basic Settings -> Text Schema -> Define Fixed Values for Texts
Best regards
Ramki

Is binding Mail step one way ? how do i send values to next step type

hi,
Is binding Mail step one way ? how do i send values to next step type. In mail task i calculated few values and sent it as mail i want those values to be sent to an activity how do i do that.
Regards,
Hari

Are you using asend mail task. If so i Think there is no requirement to bind the value from Wflow to task.
If you are using a Method other than send mail task you can bind the container element.
But I could not understand what you are doing in the method of sending mail?
Thanks
Arghadip

JEXP Type wilth accc seq JEXC in table 372 Value getting captured automa

Hi Friends,
JEXP Type with acc seq JEXC in table 372 Value getting captured automatically.
372 Sales org./Ref.doc./Ref.item
357 Country/Plant/Ctrl cod
End user have put record in 357 table and when executing the sales order the record in being copied in order but once we save the reord the value for JEXP gets automatically captured and saved under 372 table for JEXP.
can any one please throw some light on this????
Reagrds/Ashu

Hi,
Suggest you to check each of the key combination in the condition record and check the validity dates.
If there are condition records for more than one combination, then change the validity dates of all other condition record as old dates and only make the relevant condition records as either valid till current date or in to the future date.
Hope this helps.
Kind Regards
Chakradhar
Edited by: Paturi Chakradhara Rao on Jan 24, 2008 12:15 PM

RFE: Allow some types to inherit different parameterizations of same iface

I'm considering submitting this as an RFE. Does anyone think it's a bad idea or that it's impossible?
RFE: Allow some types to inherit different parameterizations of the same interface
The "proposed changes to the jls" version of the JLS3 says:
"A class may not at the same time be a subtype of two interface types which are different parameterizations of the same interface." It says nothing about superinterfaces of interfaces, but let us assume that the same restriction applies.
In some cases, this restriction seems overly broad. Assume that the type we are talking about does not simulatneously implement two parameterizations of the same interface. If the two parameterizations do not collide, because of covariant return types (or perhaps even overloading?), they should be allowed.
interface HasValue<A> {
     A getValue();
interface ObjectHolder extends HasValue<Object> {
     Object getValue();
interface StringHolder extends ObjectHolder, HasValue<String> {
     String getValue();
}What's the problem? I don't see one other than just that the JLS forbids it. Erasure or no erasure, the semantics of that kind of construct seem obvious and useful.

I'm considering submitting this as an RFE. Does anyone think it's a bad idea or that it's impossible?
RFE: Allow some types to inherit different parameterizations of the same interface
The "proposed changes to the jls" version of the JLS3 says:
"A class may not at the same time be a subtype of two interface types which are different parameterizations of the same interface." It says nothing about superinterfaces of interfaces, but let us assume that the same restriction applies.
In some cases, this restriction seems overly broad. Assume that the type we are talking about does not simulatneously implement two parameterizations of the same interface. If the two parameterizations do not collide, because of covariant return types (or perhaps even overloading?), they should be allowed.
interface HasValue<A> {
     A getValue();
interface ObjectHolder extends HasValue<Object> {
     Object getValue();
interface StringHolder extends ObjectHolder, HasValue<String> {
     String getValue();
}What's the problem? I don't see one other than just that the JLS forbids it. Erasure or no erasure, the semantics of that kind of construct seem obvious and useful.

Excise invoice created using J1IS and movement type 122

Hello
Can you please suggest whether we need to run J2IUN for the following process in order to show the debit entries in extracted RG23A PART2 register.
1. Returning the material with refernce to the original Goods receipt document (101) using MIGO movement type 122. Original GR document posted with capture and Post excise option.
2. Creaqting the Excise inoivce using J1IS with reference to material document created in Step 1
3. Releasing to accounting/ Posting the excise invoice in J1IV.
4. Extracting the Register RG23A PART 2 using J2I5
5. Print excise register using J2I6....But the debit entry not shown in register
Can you please confirm whether the debit entries in register will be updated after the Montly utilization J2IUN run ( as this process is a indirect sale process)
Please confirm
warm regards
Ramakrishna.

Hi Rama,
The accounting entries for 122 is as per standard.
for the excise invoice
Cenvat Clearing         Dr.
Cenvat Account        Cr.
for utilization
Cenvat payable          Dr.
Cenvat Account         Cr.
PLA Account              Cr.
and for MIRO it would be the standard.
you can refer the note 542862 for cin related accounting entries.
let me know if this helps you.
regards,
Adwait Bachuwar
Edited by: adwait bachuwar on Dec 21, 2010 2:21 PM

Mvmt Type 122 value different than Mvmt Type 101 value

Similar Messages

Maybe you are looking for