Problem in material

Hi guru's
iam not able to save the order.system is showing message like item is not legal.can you please guide me in this regard.

It seems that you were trying to create an export sale order and the country to which the material to be exported may be blocked from exporting.
As you would be aware Government has listed certain countries to which you are not suppose to trade. So check in TCodes like VE53 / VE56 / VE57 whether the said country is blocked.
Also update if my understanding is wrong.
thanks
G. Lakshmipathi

Similar Messages

Problem in Material create through BAPI

Hi All,
For creating MATERIAL first used BAPI_MATERIAL_GETINTNUMBER for material no generation and for creation material master BAPI_MATERIAL_SAVEDATA.
<garbled code removed>
Moderator message: Post relevant portions of the code only!
My problem is material no is not created and passing into second bapi.
Help me out of this
Edited by: Suhas Saha on Jun 17, 2011 8:01 PM

Hi Venkatesh,
*Use This Bapi :BAPI_MATERIAL_SAVEREPLICA and pass values as mentioned below.*
Use this method to create new material master data or change existing material master data. Every time this method is called, data for one or more materials can be transferred.
When new material master data is created, the material number, the material type and the sector must be sent to the method. Furthermore, a short text and the language in which the short text has been created, have to be entered. When data is being changed, only the material number need be entered.
In the header data, at least one view has to be selected for which the data is to be created. Depending on the selected view, additional mandatory parameters that have been defined as such in Customizing have to be created. If not all mandatory fields are field with data, the method ends with an error message being displayed.
First, the appropriate fields in the tables (for example, CLIENTDATA) have to be filled with data by the user. These fields must also be flagged as the method data can only be written to the database if this is the case. The user must also provide data for the appropriate fields that have been selected in a checkbox table (for example, CLIENTDATAX). Checkbox tables exist for tables that do not contain language-dependent texts (MAKT, MLTX), European article numbers (MEAN) and tax classifications (MLAN). More than one data record can be created for a material in these tables (for all materials transferred to the method).
If a structure contains fields for a unit of measure (for example, structure CLIENTDATA, field BASE_UOM), language indicator (for example, structure MATERIALDESCRIPTION, field LANGU) or country identifier (for example, structure TAXCLASSIFICATIONS, field DEPCOUNTRY) then a similarly-named field ending with _ISO also exists. In doing so, the user has the option of using the internal SAP code or the ISO code for units of measure, language indicators or country identifiers. ISO codes are converted into an SAP code for further processing. The ISO code is only used if the SAP code is not displayed. In Customizing under "General Settings", a clear assignment has to be made between the ISO codes and the SAP codes for the following activities, if you want to use ISO codes:
If a structure contains fields for units of measurement (such as structure CLIENTDATA, field BASE_UOM), language indicators (such as structure MATERIALDESCRIPTION, field LANGU), or country indicators (such as structure TAXCLASSIFICATIONS, field DEPCOUNTRY), there is always a field of the same name with the ending _ISO. This makes it possible to transfer either the internally used SAP code or a standardized ISO code for the units of measurement, language indicators, or country indicators. ISO codes are converted to an SAP code internally for further processing. The ISO code is used only if the SAP code is not transferred. If you use ISO codes, there must be a unique assignment of the ISO code to the SAP code in the following activities in Customizing for Global Parameters:
Check Units of Measurement
Define Countries
If long texts (for example, basic data texts, internal notes, purchasing info texts, material notes or sales and distribution texts) or customer-specific fields have to be created for a material, some specific characteristics have to be taken into consideration. These characteristics are detailed in the documentation for parameters MATERIALLONGTEXT and EXTENSIONIN.

Problem on Material Replication from R/3 to EBP

Hi friends,
I am having a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'. I could able to replicate Vendor and Locations from R/3 to EBP. If anybody can solve this problem.
Thanx in advance.
Raj

Hi Ahmed,
Could you please elaborate. I am getting runtime error as 'Message_Type_X' (The current application triggered as termination with a short dump).
Thanks
Raj

Problem in material superstation

HI all
Problem in material superstation when A material is get supersicate by material in that case all manual conduction is not coming for eg if I create sales order by a A material system will supercirtate that material to B material and I will add some manual conduction discount and tax save it later I want to change that quantity of that sales order from 1 quantity to 4 quantity in that case my manual conduction is not coming in sales order
Plz Help me it urgent
sageer

Hi,
If u define your condition type is manual and if you do any changes in quantity of order in change mode then manual condition will not be determined automatically. Again u have to enter it manually and then save it in change mode itself..
Regards
sankar

Problem in Material replications

Hi friends,
I am having a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'. I could able to replicate Vendor and Locations from R/3 to EBP. If anybody can solve this problem.
Thanx in advance.
SAIRAM.ALLU

Hi,
If u define your condition type is manual and if you do any changes in quantity of order in change mode then manual condition will not be determined automatically. Again u have to enter it manually and then save it in change mode itself..
Regards
sankar

Problem in material repliction

Hi friends,
I have a problem on Material replication from R/3 to EBP. I had configured all the required settings in EBP as well as in R/3. Whenever we are starting initial loading R3AS I am getting outbound queues in EBP instead of R/3. I am getting the error like 'The current application triggered a termination'.. pls solve this problem as earlyas possible .
Thanx in advance.
SAIRAM.ALLU

While defining sites for middleware in SMOEAC
we define CRM (middleware role in SRM) first on top and
the R/3(ECC) at bottom
is it reverse in your case?
BR
Dinesh

Problem loading material master (IS Mill) data from ECC to BI

Hi Gurus,
We have a problem loading Material master data from ECC to BI 7.0 SP 18.
The scenario is :
The ECC is with IS Mill... due to which the Material field MATNR is of length 40 instead of standard 18 characters.
That is data element MATNR has 18 chars and its output length is 40 chars.
When is table MARA browsed using SE16, the material with more than 18 chars.... shows only first 18 characters and are ended with !.
OMSL setting shows length as 40.
When the extractor checker runs 0MATERIAL_TEXT or 0MATERIAL_ATTR it gives correct output ..... which is more than 18 characters... not ended with !
Till here no problem.
On BI side, after replication of the datasource, i checked data element MATNR ... but it has length as 18 chars and output length as 18 chars.
OMSL setting cannot be set more than 18.
Infopackage has pulled data till PSA successfully. I checked the PSA data .... here to the material with more than 18 chars is ended with !.
When the data is further pushed to 0MATERIAL infoobject, it throws following error for all materials irrespetive of its length (example below):
0MATERIAL : Data record 768 ('SIT_PL_B01L_10_01!E '): Version 'SIT_PL_B01L_10_01! ' is not valid
0MATERIAL : Data record 165 ('RLIRS52 E '): Version 'RLIRS52 ' is not valid
Diagnosis
Data record 768 & with the key 'SIT_PL_B01L_10_01!E &' is invalid in value 'SIT_PL_B01L_10_01! &' of the attribute/characteristic 0MATERIAL.
System Response
The system has recognized that the value mentioned above is invalid, and has processed this general error message. A subsequent message may give you more information on the error. This message refers to the same value, even though it does not state this explicitly.
I did search for SAP note related to this... but could not find any.
There is one SAP note (Note 960868) which mentions about this, but the correction was then shipped with BI SP 9.... we are running on SP 18.
Requesting you all experts for help.
Best Regards,
Deepak

Hi,
follow bellow steps:
1. you need to activate the Datasouce in BI side.
Goto RSA1> Datasource> Select Datasource> Double click> Check fileds and Activate.
2. Replicate the Datasource into BI side.
3. Check the RFC connections by useing SM59.
Regards.

Problem with Materialized Views after an export

Hi @ everybody,
At an Oracle 11g R2 (11.2.0.3.0) instance, all actual CPU's/SPU's are installed, on a Red Hat 6 Machine i have a problem with Materialized Views from a schema, which i have exportet from an old database machine on Oracle 10g (10.2.0.1.0) to the new machine.
I've exportet with the old exp and imported with imp, because i know, that i get some strange errors because of the materialized views when i'm using the new expdp and impdp tools.
At the old machine the materialized views are so programmed, that they get an update of data at a defined time like this:
START WITH TRUNC(SYSDATE) + 21/24
      NEXT SYSDATE+1
...But after the export this "update function" of the materialized view is not available. So i have deleted that views and recreated them with the START WITH parameters. So now they are running.
But why do i have this problem?
Is this "START WITH" somewhere written as a job or so in, for example, DBMS_SCHEDULER or something else? So i had forgotten to export these jobs or where is that defined?
Is this a bug?
Thanks for answers and help!
Best regards,
David

I can't remember the error of expdp/impdp. That is some days ago, i have to rebuild this.
I think in my scenario for the import i don't need the TABLE_EXISTS_ACTION, because by importing at the new server i've just createt the naked tablespace for the data and the users, not more. So he didn't has something to overwrite.
And i have to tell you: i'm just the dbA. The desining of the tables and materialized views is many years ago by installing the old server. I'm just to young in my company to know about the design of the instance and why it was designed so.
Anyway: my problem is, that after the import of the schemas to a new server the "START WITH" option in the materialized views is not there anymore and i just want to why so i can think about a solution for that and create it with the database designers of my company.
EDIT: And here are the SQL Statements for creating the Materialized Views:
First, at the OLD Server (Oracle 10g 10.2.0.1.0)
CREATE MATERIALIZED VIEW "DUPONT_CCG2_P"."PR_PRODUCT_ITEMS"
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "DUPONT_14523"
BUILD IMMEDIATE
USING INDEX
REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1
USING DEFAULT LOCAL ROLLBACK SEGMENT
DISABLE QUERY REWRITE
AS (SELECT DISTINCT
      PR_CUSTOMER_MASTER_DATA.CLIENT_ID,
      PR_CUSTOMER_MASTER_DATA.ILN_USER,
      PR_ARTICLE.EAN,
      PR_ARTICLE.CODE,
      PR_USED_ARTICLE_TEXT.ARTICLE_TEXT,
      PR_USED_ARTICLE_TEXT.LANG_CODE,
      PR_ARTICLE.SUP_ITEM_NO,
      PR_ARTICLE.OLD_ITEM_NO,
      PR_COMPANY_ITEM_MATCH.ITEM_BY_NO,
      PR_COMPANY_ITEM_MATCH.UOM_UNIT,
      PR_COMPANY_ITEM_MATCH.PRICE_UOM,
      PR_COMPANY_ITEM_MATCH.PRICE,
      PR_COMPANY_ITEM_MATCH.CURRENCY,
      PR_COMPANY_ITEM_MATCH.PRICE_QTY,
      PR_COMPANY_ITEM_MATCH.SALES_UNIT,
      PR_COMPANY_ITEM_MATCH.START_DATE,
      PR_COMPANY_ITEM_MATCH.END_DATE,
      PR_ARTICLE.UPDATED_AT
        FROM PR_ARTICLE, PR_COMPANY_ITEM_MATCH, PR_USED_ARTICLE_TEXT, PR_CUSTOMER_MASTER_DATA, PR_ADDRESS
        WHERE PR_ADDRESS.ORDER_TYPE='REP'
      AND PR_CUSTOMER_MASTER_DATA.ILN_USER=PR_ADDRESS.ILN_USER
      AND PR_COMPANY_ITEM_MATCH.ILN_USER=PR_ADDRESS.ILN_LINK
      AND PR_CUSTOMER_MASTER_DATA.SALES_ORG=PR_COMPANY_ITEM_MATCH.SALES_ORG
      AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_COMPANY_ITEM_MATCH.CLIENT_ID
      AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_ADDRESS.CLIENT_ID
      AND PR_ARTICLE.SUP_ITEM_NO=PR_COMPANY_ITEM_MATCH.SUP_ITEM_NO
      AND PR_COMPANY_ITEM_MATCH.SALES_ORG=PR_USED_ARTICLE_TEXT.SALES_ORG
      AND PR_ARTICLE.SUP_ITEM_NO=PR_USED_ARTICLE_TEXT.SUP_ITEM_NO
      AND PR_CUSTOMER_MASTER_DATA.LANG_CODE=PR_USED_ARTICLE_TEXT.LANG_CODE
      AND ( PR_COMPANY_ITEM_MATCH.END_DATE IS NULL OR to_date(PR_COMPANY_ITEM_MATCH.END_DATE,'YYYYMMDD') - sysdate > 0)
      AND ( PR_COMPANY_ITEM_MATCH.START_DATE IS NULL OR sysdate - to_date(PR_COMPANY_ITEM_MATCH.START_DATE,'YYYYMMDD') > 0)
)And here the at the NEW Server (Oracle 11g R2 11.2.0.3.0)
CREATE MATERIALIZED VIEW "DUPONT_CCG2_P"."PR_PRODUCT_ITEMS" ("CLIENT_ID", "ILN_USER", "EAN", "CODE", "ARTICLE_TEXT", "LANG_CODE", "LANR", "OLD_LANR", "ITEM_BY_NO", "UOM_UNIT", "PRICE_UOM", "PRICE", "CURRENCY", "PRICE_QTY", "SALES_UNIT", "START_DATE", "END_DATE", "UPDATED_AT")
ORGANIZATION HEAP PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255
NOCOMPRESS LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1
BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE DEFAULT)
TABLESPACE "DUPONT_14523"
BUILD IMMEDIATE
USING INDEX
REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1
USING DEFAULT LOCAL ROLLBACK SEGMENT
USING ENFORCED CONSTRAINTS DISABLE QUERY REWRITE
AS (SELECT DISTINCT
      PR_CUSTOMER_MASTER_DATA.CLIENT_ID,
      PR_CUSTOMER_MASTER_DATA.ILN_USER,
      PR_ARTICLE.EAN,
      PR_ARTICLE.CODE,
      PR_USED_ARTICLE_TEXT.ARTICLE_TEXT,
      PR_USED_ARTICLE_TEXT.LANG_CODE,
      PR_ARTICLE.SUP_ITEM_NO,
      PR_ARTICLE.OLD_ITEM_NO,
      PR_COMPANY_ITEM_MATCH.ITEM_BY_NO,
      PR_COMPANY_ITEM_MATCH.UOM_UNIT,
      PR_COMPANY_ITEM_MATCH.PRICE_UOM,
      PR_COMPANY_ITEM_MATCH.PRICE,
      PR_COMPANY_ITEM_MATCH.CURRENCY,
      PR_COMPANY_ITEM_MATCH.PRICE_QTY,
      PR_COMPANY_ITEM_MATCH.SALES_UNIT,
      PR_COMPANY_ITEM_MATCH.START_DATE,
      PR_COMPANY_ITEM_MATCH.END_DATE,
      PR_ARTICLE.UPDATED_AT
        FROM PR_ARTICLE, PR_COMPANY_ITEM_MATCH, PR_USED_ARTICLE_TEXT, PR_CUSTOMER_MASTER_DATA, PR_ADDRESS
        WHERE PR_ADDRESS.ORDER_TYPE='REP'
      AND PR_CUSTOMER_MASTER_DATA.ILN_USER=PR_ADDRESS.ILN_USER
      AND PR_COMPANY_ITEM_MATCH.ILN_USER=PR_ADDRESS.ILN_LINK
      AND PR_CUSTOMER_MASTER_DATA.SALES_ORG=PR_COMPANY_ITEM_MATCH.SALES_ORG
      AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_COMPANY_ITEM_MATCH.CLIENT_ID
      AND PR_CUSTOMER_MASTER_DATA.CLIENT_ID=PR_ADDRESS.CLIENT_ID
      AND PR_ARTICLE.SUP_ITEM_NO=PR_COMPANY_ITEM_MATCH.SUP_ITEM_NO
      AND PR_COMPANY_ITEM_MATCH.SALES_ORG=PR_USED_ARTICLE_TEXT.SALES_ORG
      AND PR_ARTICLE.SUP_ITEM_NO=PR_USED_ARTICLE_TEXT.SUP_ITEM_NO
      AND PR_CUSTOMER_MASTER_DATA.LANG_CODE=PR_USED_ARTICLE_TEXT.LANG_CODE
      AND ( PR_COMPANY_ITEM_MATCH.END_DATE IS NULL OR to_date(PR_COMPANY_ITEM_MATCH.END_DATE,'YYYYMMDD') - sysdate > 0)
      AND ( PR_COMPANY_ITEM_MATCH.START_DATE IS NULL OR sysdate - to_date(PR_COMPANY_ITEM_MATCH.START_DATE,'YYYYMMDD') > 0)
)The own differences i can see is at the "header". In the new one is the NOCOMPRESS LOGGING Option and in the first line the code has the columns diretcly defined.
But, i think, for my problem this line is determining:
REFRESH COMPLETE ON DEMAND START WITH sysdate+0 NEXT SYSDATE+1And this line is the same at both server.
Edited by: David_Pasternak on 12.04.2013 00:06

Problem with material and document date in sales order

Hi All,
I am working in ECC 6.0 .I am facing problem with two fields when in enter in to sales order(tcode:va01)
1.A material comes automatically in line item.
2.Document date also comes as 27.03.2008 instead of todays date in each order i create.
I think its not related to configuration.I think its related to some modifications through exits or enhancement points.could someone suggest me a where to check and solve that.
Your's suggestion is appreciated.

Hi Sharad,
Check MV45AFZZ include in se38..It is a user exit for basic validation on sales...We may be able to find some code there (if screen data is predefined by code as mentioned)
Hope it helps
Regards
Byju

Free goods problems changing material

Hello,
I am using free goods inclusive without item generation (NRAB condition).
I introduced a material A having free goods, ant it works fine, but if I change the material A for B in the same position (without free goods), the NRAB condition is maintained.
Has anyone seen this bug? Is there a note with this problem? I have searched it without successful.
(I am using SAP ECC 6.0
Alberto.

I suppose it disappears once you change qty (after you changed material A to B) ?

Problem with Material Confirmation (Availability Check)

Dear All,
There is a problem with the availability check. when i place order system does availability check and confirms the order. Now say for example i have 100qty of material - X and i created order for 50qty, system confirmed and then i went on creating orders for this , say i have created orders for it for 150qty, so system has confirmed 100 and 50 on future date.
Now when i try to do the delievry for the first order(50 qty), system gives me an error that "0" qty is available.
Can you please tell me what may be the reason for this.
Thanks,

You can also check in T-code Co09 of the availability. Best and easy one to read for me has been MD04 Transaction code.
What system does in Sales Order is that it plans the requirement taking into consideration Material availability and if material doesn't exist but sees that in a few days in the future material will be available so system confirms it. Note that physically the material may not even be present. You find out if you really have physical stock in the delivery. For example in the sales order in the future the system sees that a Purchase Order will take place so system confirms it. Even though physically you have not even done a goods receipt for that PO. So any Sales Order which has been created before holds that reservation. So if you make a PO goods receipt in the future all those sales order has taken up this stock even. So the new sales order you created may not even have physical stock present or available as back order exists.
If you delete Deliveries that have not had PGI done to them this will take the requirement out of the list of Deliveries you can see this in MMBE if you scroll to the right. You can also do reason for rejection for other old orders to take out reservation in MD04.
Good Luck
Ali Lozada

Problem in materialized view

Hello everybody!!!
I used the following script in order to see the automatic refresh of data contained in a materialized view.
I used the following script in SCOTT schema:
create materialized view log on emp
with rowid (job,sal)
including new values
create materialized view emp_mv
build immediate
refresh fast on commit
as
select job , sum(sal) sum_sal
from emp
group by job
The problem is that after i update the sal column (and commit it) of an employee and selecting from the emp_nv , I DO NOT see any difference , although the materialized view log has been updated successfully!!!
Under which circumstances the materialized view would be updated as well?
Simon.

What is job_queue_processes set to on your system? Materialized view refreshes are generally done as background jobs, so that initializiation parameter needs to be set to a non-zero value.
Justin

Problem in Material Extension

Hi!
When I extent one material to a plant->sales organization->Dist. Channel, it is extending in all the plants assigned to that sales organization->distr. channel.
Can anybody help me to solve this problem?
Thanks and regards
Biswajit

Hi!
Thanks to all for the reply. But I have not get any solution from these replies. My problem is when I extent the material in a single plant in a sales org., dist channel, material is extending in all the plant assigned under the sales org., dist, channel automatically. This is not the proper thing happenning.
Pl. give the solution for this.
Thanks
Biswajit Datta

Problem with Materialized Views in 10g

Hi All,
I am creating a Materialized View like
CREATE MATERIALIZED VIEW mvname TABLESPACE SYSTEM BUILD IMMEDIATE REFRESH WITH ROWID FOR UPDATE AS ( SELECT a,b,c FROM table_a,table_b,table_c WHERE cond );
I am getting an error
SQL Error: ORA-12013: updatable materialized views must be simple enough to do fast refresh.
Can anyone tell what is the problem?
I have included rowid of all three tables in select clause.

Hi,
From Oracle Docs:
ORA-12013: updatable materialized views must be simple enough to do fast refresh
Cause: The updatable materialized view query contained a join, subquery, union, connect by, order by, or group by caluse.
Action: Make the materialized view simpler. If a join is really needed, make multiple simple materialized views then put a view on top of them.
Regards
K.Rajkumar

Problem with material number

I created a material 20070730a1 using mm01 tcode. But in my program when i am trying to retrieve info for that material the select statement is unsuccessfully. But when i go for that material in mm03 i am able to view info for that material. Even i am using CONVERSION_EXIT_MATN1_INPUT FM to convert my materal number and i am using the return value from this function in my select statement. But still the select statement fails.
code is as follows:
FORM conversion_exit USING pv_matnr       TYPE matnr
                   CHANGING pr_temp_matnr TYPE char18.
CALL FUNCTION 'CONVERSION_EXIT_MATN1_INPUT'
    EXPORTING
      input        = pv_matnr
    IMPORTING
      output       = pr_temp_matnr
    EXCEPTIONS                                              "#EC *
      length_error = 1
      OTHERS       = 2.
ENDFORM.                    " conversion_exit
pr_temp-matnr is send to an internal table i_cabn from there it used in select statement.
FORM get_mat_type.
IF NOT i_cabn IS INITIAL. "check for initial
    SELECT matnr                                        "#EC CI_NOFIELD
           matkl
           pstat
      FROM mara
      INTO TABLE i_matn
       FOR ALL ENTRIES IN i_cabn
     WHERE matnr             = i_cabn-old_matnr
       AND   lvorm             <> c_x.
    IF sy-subrc = 0.
      SORT i_matn BY matnr.
    ENDIF. " IF sy-subrc = 0
ENDIF.    " IF NOT i_cabn IS INITIAL
ENDFORM.                    " get_mat_type
Any suggestion on this problem.
Thanks

got it

Problem with materialized views

I have a problem with the use of materialized views.
I make this procedure:
1: I create a table with the results of a query
2: Create a materialized view in that prebuilt table
Problem: When i execute the query after creating the materialized view i receive this error from oracle : ora-00903 table do not exists.
I get that error in 10% of the materielized views that i create that way, anyone can tell me what is the problem?

I'm using Oracle 9.2.0.5.0
query rewrite disabled

Problem in material

Similar Messages

Maybe you are looking for