Problem while updating IDOC MATMAS03.

Hi All,
We are creating outbound Material master IDOC with basic type as MATMAS03.Standard FM MASTERIDOC_CREATE_MATMAS is being used to create IDOCs.Field MEINH of E1MARMM segment is getting populated with ISO standard UOM value .In debugger I can see that ISO value of UOM is geeting passed , but when I display the IDOC in WE05 it doesnt show me ISO value of UOM, it show original value .
For Example, for certain UOM X ISO CODE is Y then should get updated in E1MARMM-MEINH but when see in WE05 it shows me X even though debugger shows updated value as Y.
can somebody please share thought what is the reason behind this?
Thanks
Saurabh

Hi Joshi
What Qualifier you using in E1MARMM MSGFN (Function)
Ramesh

Similar Messages

Problem while updating the Support Package 17 on my SAP WAS SP9

Hi,
I'm facing problem while updating the Support Package 17 on my SAP WAS SP9
ERROR 2006-10-13 10:23:22
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).
Please help me in this regard.....
Thanks in advance...
Satya

Hello gentlemen, I am also having problem with the following running on 64 bit Windows and SQL2005/64 bit. I am erroring in Step 8 'Updating JDBC' driver. I am attempting to update from SP9 to SP18. The WEBAS Jave installed went flawless but I seem to be stuck here. Any help is appreciated...
ERROR 2006-11-22 10:13:57
FSL-06002 Error 2 (The system cannot find the file specified.
) in execution of a 'CreateProcess' function, line (284), with parameter (java.exe ...).

Facing problem while updating IInfotype 0009-bank details through workflow

Dear SAP Gurus,
I am facing a problem while updating Infotype 0009 through workflow which is integrdated with portal.
Scenario:
Employee logins to portal and changes his/her bank details like payee name, bank key, account number, postal code and city of bank, bank name etc.
Once he submits the request, my workflow is triggered through SAP_WAPI_START_WORKFLOW which is called from portal and goes through various approval steps and finally reaches the step where the container elements are finally to be updated in IT0009.
Field bank account number (BANKN), which is part of table PA0009 are easily updates using the FM HR_INFOTYPE_OPERATION by first enqueuing the employee number and after the update dequeuing it.
However fields like payee name (EMFTX) bank key (BANKL) , bank name(BANKA -structure BNKA_BF-this is automatically fetched based on bank key) and postal code(BKPLZ) and city of bank (BKORT) are from structure Q0009 (on the infotype 9 screen level) and from table BNKA (at table level). The problem is that these are not getting updated by HR_INFOTYPE_OPERATION as they are not the part of infotype 9.
Can anyone help me to understand how can these fields be updated ?
Quick help will be highly appreciated.

Hi Spantaleoni,
Thanks for your quick response.
Well actually the table BNKA is a master table for the bank information and we must not create entries in it or update the table programatically, rather we should use the available data in it.
Now say employee currently has bank as A and he wants to change it as B which is available in BNKA then he will just select the bank B from search help provided in portal which again comes from table BNKA only. Employee then submits the info and it must get updated in the infotype PA0009.
As far as think, this should be done on screen level of infotype PA0009 as I have already mentioned that certain fields are coming from structure Q0009 and they cannot be updated on PA0009 table level.
I am just looking for way through which I can update the screen of infotype PA0009 of employee through workflow.
Regards

There was a problem while updating ios 7.1 now my ipad isnt starting up just shows a symbol of itunes with a arrow towards it with its USB cable

there was a problem while updating ios 7.1 now my ipad isnt starting up just shows a symbol of itunes with a arrow towards it with its USB cable

YOU ARE IN RECOVERY MODE
1. Turn off iPad
2. Turn on computer and launch iTunes (make sure you have the latest version of iTune)
3. Plug USB cable into computer's USB port
4. Hold Home button down and plug the other end of cable into docking port.
DO NOT RELEASE BUTTON until you see picture of iTunes and plug
5. Release Home button.
ON COMPUTER
6. iTunes has detected iPad in recovery mode. You must restore this iPad before it can be used with iTunes.
7. Select "Restore iPad"...
Note:
1. Data will be lost if you do not have backup
2. You must follow step 1 to step 4 VERY CLOSELY.

Problem while updating Delivery date uisng BAPI_PO_CHANGE

Hi friends,
Iam facing a problem while updating delivery date of a purchase order using the bapi BAPI_PO_CHANGE
After the bapi is getting triggered iam geting sy-subrc = 0
But in the return parameters iam getting 3 error messages so iam unable to update the delivery date..
Error meesage which iam getting are
a) Purchase order still contains faulty items
b) Enter Tax Code
c) Instance 1000001 of object type PurchaseOrder could not be changed.
How can i correct it..
Please find my code below
LOOP AT it_eket INTO wa_eket.
    wa_poschedule-po_item = wa_eket-ebelp.
    wa_poschedule-sched_line = wa_eket-etenr.
    wa_poschedule-delivery_date = wa_eket-eindt.
    APPEND wa_poschedule TO poschedule.
    wa_poschedulex-po_item = wa_eket-ebelp.
    wa_poschedulex-sched_line = wa_eket-etenr.
    wa_poschedulex-po_itemX = 'X'.
    wa_poschedulex-sched_lineX = 'X'.
    wa_poschedulex-delivery_date = 'X'.
    APPEND wa_poschedulex TO poschedulex.
READ TABLE IT_EKPO INTO WA_EKPO WITH KEY EBELN = WA_EKET-EBELN
                                         EBELP = WA_EKET-EBELP.
      IF SY-SUBRC = 0.
      WA_POITEM-PO_ITEM = WA_EKPO-EBELP.
      APPEND WA_POITEM TO POITEM.
      WA_POITEMX-PO_ITEM = WA_EKPO-EBELP.
      WA_POITEMX-PO_ITEMX = 'X'.
      APPEND WA_POITEMX TO POITEMX.
     ENDIF.
    CALL FUNCTION 'BAPI_PO_CHANGE'
      EXPORTING
        purchaseorder = wa_eket-ebeln
      TABLES
        return        = t_bapiret2
        POITEM        = POITEM
        POITEMX       = POITEMX
        poschedule    = poschedule
        poschedulex   = poschedulex.
    READ TABLE t_bapiret2 INTO wa_bapiret2 WITH KEY type = 'E'.
    IF sy-subrc NE 0.
      CALL FUNCTION 'BAPI_TRANSACTION_COMMIT'
* EXPORTING
*   WAIT          =
* IMPORTING
*   RETURN        =.
      IF sy-subrc = 0.
        WRITE : 'DELIVERY DATE UPDATED'.
      ENDIF.
    ENDIF.
how can i correct it...
Regards
Kumar

Hi,
Pass the following values...
POACCOUNT LIKE BAPIMEPOACCOUNT...
poaccount-TAX_CODE = ? (value)....
That should take care of the missing field.
Regards,
Madan..

Access Privileges problem while updating ipod

Access Privileges problem while updating ipod
so im having troubles updating my ipod when i attempt to update it i get a message that says The ipod "Mitch" cannot be updated you do not have enough access privileges for this opperation
some of my things are updated but not all
any help would be greatly appreciated!
Dell Windows XP

hi j.block!
hmmmmmmmmmmm. one other thing that might be worth a try if all else fails. i have once seen something like this turn out to be caused by a really kinky version of this issue:
iTunes: "privileges" or "permissions" issue when importing audio CD or adding music to library
... where the permissions were odd on the ipod itself ... but i've only seen that happen once. it's probably worth checking on only if nothing else seems to be working for you.
love, b

Problem while sending IDOC to File Senario

Hi Experts
    I am having problem while sending the Idoc from SAP R/3 to File
   I have done all the setting in SAP as well in XI but while pushing IDOC
   I am getting error in the transaction sm58 in SAP R/3
" <b>The service for the client 300(My SAP R/3 client) is not present in Integration
Directory</b>"
I can any one explain me what to done on this....all the connections are fine
Waiting for Response
Adv points and thanx
Rakesh

Reason and Prerequisites
You send IDocs from system ABC to the exchange infrastructure (XI) of system XIZ, and error messages are issued in system ABC (Transaction SM58) for the IDOC_INBOUND_ASYNCHRONOUS function module.
This note proposes solutions for the following error messages:
a) No service for system SAPABC client 123 in the integration directory
b) Transaction IDX1: Port SAPABC, client 123, RFC destination
c) ::000
d) NO_EXEC_PERMISSION: "USER" "Business_System"
e) IDoc adapter inbound: Error error ...
Solution
a) Error message: No service for system SAPABC client 123 in the integration directory
Solution:
You send IDocs from system ABC to XI. In the control record of the IDoc, the SNDPOR field contains the value "SAPABC". The client of the sending system is determined by the MANDT field of the control record. The system ID and client are then used to determine a service without party of the type (business-system/business-service):
Business system
Activities in the System Landscape Directory (SLD)(Create technical system):
Create a technical system for system ABC in the SLD, and create the client for this. Do not forget to assign an "ALE logical system" (for example, "ABCCLNT123") to this technical system.
SLD (Business system):
You can now explicitly assign a business system to this client.
For more details, refer to the SLD documentation.
Activities in system ABC (self-registration in the SLD):
Alternatively, you can register the system in the SLD in system ABC with Transaction RZ70. You will find detailed information about the SLD registration of systems on the SAP Service Marketplace for the "Exchange Infrastructure" in the document "Exchange_Installation_Guide.pdf".
In system ABC, you can check your configuration with TransactionSLDCHECK.
Activities in Integration Directory (import business system from SLD):
You will find the business systems under Services Without Party in the Integration Services. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Use the Import/Update button to copy the data from the SLD, to create business systems, or to update their identifiers.
Business service
Activities in the Integration Builder directory:
You want to create a service without party that is not part of your system infrastructure and is therefore not maintained in the SLD.
In the Integration Builder directory, you will find the "Business-Services" under Services Without Party. In the Service menu, you will find the system identifiers, the client, and the corresponding ALE logical system under "Objects"->"Adapter-specific identifiers".
Activate the change list in Integration Directory.
In system ABC, you can restart the incorrect entry from Transaction SM58 .
b) Error message: Transaction IDX1: Port SAPABC, client 123, RFC destination
Solution:
The Integration Server tries to load the IDoc metadata from the sending system. The IDoc schemas from the Integration Repository cannot be used because they are release-dependent.
The sending system is determined by the value of the "SNDPOR" field from the IDoc control record (for example, "SAPABC").
Activities in the central XI system:
In Transaction IDX1, you can assign an RFC destination to the sending system (for example, "SAPABC"). This must be created beforehand in Transaction SM59.
Note that the IDoc metadata is cross-client data. In Transaction IDX1, only one entry must be maintained for each system. Only the lowest client is used by the runtime for Idoc metadata retrieval with RFC.
Ensure that only SAPABC and not "SAPABC_123" is entered in the port name.
c) Error message: "::000"
Solution:
This error occurs if the central XI system tries to load the IDoc metadata from the sending system by RFC.
There may be several different reasons for the failure of the metadata import, the error is not transferred in full by tRFC completely, and this results in the error message above.
User cannot log onto sending system
User/password/client is not correct or the user is logged due to too many failed logons.
Activities in sender system ABC:
Transaction SM21 contains entries for failed logons.
Activities in the central XI system:
Determine the sending port from the IDoc control record of the IDoc. If the ID of the sending system has the value "ABC", the value of the sending port is "SAPABC". You will find the RFC destination used for the "SAPABC" sending port with the lowest client in Transaction IDX1. In Transaction SM59, you will find the RFC destination containing the maintained logon data .
User does not have the required authorizations
Activities in the sender system ABC:
In Transaction SM21, you will find entries relating to authorization problems and more exact details.
Contact your system administrator and, if necessary, assign the user the required roles in user administration.
IDoctyp/Cimtyp cannot be loaded
Activities in sender system ABC:
In the sender system, you can check your IDoc types in Transaction WE30 (IDoc type editor) Take note not only of the errors, but also of the warnings.
The most common errors are:
- IDoc type or segments not released
- Segments that no longer exist are listed in the IDoc type
- Data elements that do not exist in the DDIC are assigned to fields
in the segment.
Contact your system administrator and correct these errors in the IDoc type.
d) Error message: NO_EXEC_PERMISSION: "User" "Business_System"
Solution:
You created a list of users in the directory who are authorized to use the "Business_System". The user in the error message is not on the list.
Alternatively, the same error is used if you have created a sender agreement with a channel of the IDoc type for the "Business_System" and the interface used. The user in the error message is not contained in the list of all authorized users defined there.
e) Error message: IDoc adapter inbound: Error error
Solution:
You send IDocs to the central XI system, where they are received by the IDoc adapter. The IDocs are converted into IDoc XML, and a corresponding XI message is generated and transferred to the XI Runtime Engine. The Engine tries to read its own business system from the "Exchange Profile". If the Exchange Profile is currently unavailable, the message is not processed and it is returned to the sending system with an error message.
Regard's
Prabhakar.....

Problem while update and insert data in table

Hi All,
I have problem while save line data....
I have an advance table.I take remove and duplicate line in message choice of advance table action layout.
Also there is one temp table to save Po number data which is populated in advance table according to PO Number search.And In Temp table record number is column which use
to insert and update data in temp table which mention in procedure
Problem is that : When i Searched PO Number and duplicate line and save that record it insert a new line always and it insert record according to duplicate line no .It not update previous line,insert new line always according to duplicate line no.
Please tell me what is solution?
Thanks,
Neil

Hi,
I am not cleared with your requirement.
If possible send me the screenshots for the same.
--Sushant
[email protected]

Problem while updating Item category using Bapi_salesorder_change

Hi,
Iam facing a probelm while updating item category using bapi Bapi_salesorder_change
In the Return table iam getting the folowing mesages.
Inforation mesage : Field 'PSTYV' cannot be changed, VBAPKOM 000010 ready for input
Error Message : Item 000010 cannot be processed.
Please find the code below
CLEAR wa_bapisdh1x.
wa_bapisdh1x-updateflag = 'U'.
CLEAR wa_order_item_inx.
wa_order_item_inx-itm_number = wa_vbap-posnr.
wa_order_item_inx-item_categ = 'X'.
wa_order_item_inx-UPDATEFLAG = 'U'.
APPEND wa_order_item_inx TO it_order_item_inx.
CLEAR wa_order_item_inx.
CLEAR wa_order_item_in.
wa_order_item_in-itm_number = wa_vbap-posnr.
wa_order_item_in-item_categ = 'ABC'.
APPEND wa_order_item_in TO it_order_item_in.
CLEAR wa_order_item_in.
CALL FUNCTION 'BAPI_SALESORDER_CHANGE'
    EXPORTING
      salesdocument    = w_vbeln
      order_header_inx = wa_bapisdh1x
    TABLES
      return           = it_return
      order_item_in    = it_order_item_in
      order_item_inx   = it_order_item_inx
How can i correct it..
Regards
Kumar

Actually iam facing a strange problem here.
When i copy the program into another sample program and execute it iam able to change both the item catgegory and delivery block for particular sales order and item number.
But in my main program i have BDC for MB1B transaction to create the material document.
Once the material document is created succesfully iam using BAPI Sales_order_change to change the item category and delivery block..
In my main program iam not to change the item catgeory getting an error field PSTYV cannot be changed.
But the same code is running percfectly in the copied one..
How can i correct that..
Regards
Kumar

Connection lost problem while updating my Nokia As...

Dear All,
I face a connection lost problem while I am updating Nokia Asha 200 using Nokia Suite
I installed Nokia software too many times, and tried to repair it. Also, I used another USB cable, but the problem still happen
While it is installing the software, it suddenly stops and show connection lost to your phone.
When I try to restart and reconnect the USB cable, the problem still happen
Nokia200
V 10.61
02-03-12
RM-761
Thanks in advance

Dear Farby
Thanks for your kind and quick reply.
please note that I tried again now, and when the messages for connection lost appears again, I waited for 5 minutes, and nothing happens
because it shows me to do steps, as follows :
1. Disconnect USB cable from phone.
2. restart your phone
3. reconnect the USB cable
4. Wait for the installation to continue.
and when I do these steps, the phone restarts in a test mode, all I see is a test mode message over its screen.
I believe that this is a fatal error which happens through the installation process and which leads to unsuccessful installation
I lost hope in updating the software of this phone, escaially I need to do so, because I face problems with these phone, which doing a hard reset even don't fix.
Thanks again, Farby ... for your help
Regards,

Problem while updating notification at ITEM level ?

Hi...
I am doing an LSMW to update certain notifications at item level.
The Function module which i am using for this purpose is ..
IQS4_MODIFY_NOTIFICATION
While updating the first line item of notification, it is successfully updated, but while updating the second line item of the notification and further line items, error is thrown stating .....
"Notification is locked by the user"
I want to release this lock of notification after every change in line item. How do i do this.
Regards.
Edited by: Akshay Raj on Oct 16, 2008 8:32 AM
Edited by: Akshay Raj on Oct 16, 2008 8:43 AM

Use userexit save_document_prepare in MV45AFZZ .
<REMOVED BY MODERATOR>
Edited by: Alvaro Tejada Galindo on Jun 12, 2008 6:51 PM

Facing Problem while updating SAP Note for ESI Limit

Hello,
While Updating ESI Note 0001465628, Step 4 i.e Enable the feild in the cluster 'ESI'. When ABAP'er execute a report RPUGDF00 through SE38 he is getting "Internal Table" radio button option instead of payroll.
If he enters "Internal Table" feild but he is not getting "f" substep feilds in step 4.
Can anybody please guide me to update this note.
Edited by: sunitaos on May 28, 2010 2:43 PM

HI,
Just go thru the list of following notes related to ESI.
Note No     Description     Date
1465628     ESI Limit increased and length of temp. ESI no increased     12.05.2010
1441625     Length of ESI number is change     29.03.2010
1415952     Change in ESI Eligibility limit for physically disabled Ees     20.02.2010
1432975     Length of ESI No     15.02.2010
1425068     ESI FORM 5:Addition of Dispensary information     29.01.2010
1347850     ESI Reporting-Inconsistent in case of org. reassignment     10.01.2010
1403619     ESI Form 5 - Sorting based on ESI Insurance number     30.11.2009
1410113     ESI limit for Disabled Ees     24.11.2009
1409580     ESI Form 5: Add Dispensary Information     20.11.2009
1401519     ESI Retro Treatment     29.10.2009
1392870     ESI Form5:Allignment of the text inconsistent for PDF layout     12.10.2009
1383672     HINCALC0: For split in IT27 after termination, payroll dumps     09.09.2009
1348534     ESI: /3E1 and /3E2 are inconsistent in case of retro run     18.06.2009
1344386     ESI Treatment in case income recieved during inactivity     31.05.2009
1327118     Form 16 - Export data from Temse to PCL4 for previous years     13.04.2009
1290863     Error while generation of Form 6 in ESI report     18.03.2009
1247107     ESI Form 5 - New Layout     06.11.2008
1244296     ESI Form 5 - New Layout     22.08.2008
506128     Legacy data transfer     25.06.2008
1177470     ESI New Form6- Total is missing in worksheet     17.06.2008
1172216     ESI Form 6 - Remarks is missing in PDF Layout     27.05.2008
1164880     ESI Form-6 & Form7-Inconsistent in case of splits in IT0001     23.05.2008
1140970     New ESI Form Layout     23.05.2008
1071281     PY-IN: Master Note for FY 2007-08 (Developments)     02.01.2008
1117371     Double deduction in ESI for employee during retro     26.11.2007
1099052     ESI Form 7 throws error when printing     05.10.2007
1071945     ESI Monthly Eligibility report progarm     05.07.2007
1069980     Executing report program HINCESI0 for multiple payroll areas     29.06.2007
1048358     ESI form 6: Effect of IT0001 split     20.04.2007
1032446     Enabling correction offcycle payroll run     02.04.2007
Thanks & Regards,
Param

Problem while updating Data through IDOC

hi!
I have declared an Internal Table like a structure which has 10 fields.
To generate Idoc i need to pass the records from Internal Table to EDIDD-SDATA.
Since SDATA is a string of Char 1000, i'm concatenating all the columns of internal table to a variable.
In debug mode all the fields size are adopting to its correct size.
but after generating the IDOC and view through WE02 the data are miss placed bz of inclusion of space.
Example:
field1 (Size 4) - ABCD
field2 (Size 10) - 0000001234
field3 (size 10) - 09.02.2010
field4 (Size 6) - _12345
field5 (Size 4) - 6 AB --> missed character is continuing in next field after a space data of its corresponding field starts
field6 (Size 3) - C 2 -->missed character is continuing in next field after a space data of its corresponding field starts
Tried by suppressing the space. CONDENSE NO-GAPS. . . .it dnt help me
How to solve this
Regards
Kv

Hi,
Populate it this way :-
LOOP AT IT_DATA into wa_data.
CALL METHOD CL_ABAP_CONTAINER_UTILITIES=>FILL_CONTAINER_C
    EXPORTING
      IM_VALUE               = WA_DATA
    IMPORTING
      EX_CONTAINER           = EDIDD-SDATA
    EXCEPTIONS
      ILLEGAL_PARAMETER_TYPE = 1
      others                 = 2    .
append EDIDD.
ENDLOOP.
Thanks,
Best regards,
Prashant

Namespace problem while updating a desktop app

Hello,
I've searched on a lot of forums but didn't find anything accurate on my problem.
I have an old AIR 2.0 desktop app that updated itself.
I want to update it to the last 3.4 framework. So I followed instructions for the intermediate application to update (between 2.0 and 2.5).
I manage to update from 2.0 to a Air 2.5 intermediate application, while still having the 2.0 namespace in the app descriptor file.
But it is impossible for me to update this 2.5 application (with 2.0 namespace) to a 2.5 namespace !!
Here si my update descriptor file :
<?xml version="1.0" encoding="UTF-8"?>
<update xmlns="http://ns.adobe.com/air/framework/update/description/2.5">
           <versionNumber>0.3.2</versionNumber>
           <versionLabel>Version for 0.3.2</versionLabel>
     <url>http://www.mywebsite/app.air</url>
     <description><![CDATA[
Final test
           ]]></description>
</update>
But I'm having the error 16831 : "Application namespace and update.xml namespace are not compatible".
It seems that my application only wants to update to another one with the exact same namespace.
How this can be ?
Thanks !
I must say that I publish to AIR 2.5 with Flash CS5 and flashpro extension for air (in beta version) as Flash CS6 always overwrite the app descriptor while publishing (so it is impossible to change the namespace to 2.0 for example)

Ok, after having searched a lot, I managed to understand what was going on....
To those interested, the update descriptor must stay in a 1.0 namespace until the end of the process.
When all is updated (app namespace to 2.5), you can use the 2.5 update descriptor namespace....

Problem while updating record in the database

I have created an entity object, view object and a form to show that. whenever i update some field in the form and try to commit the change, exception is thrown stating that-
(oracle.jbo.DMLException) JBO-26080: Error while selecting entity for Countries
----- LEVEL 1: DETAIL 0 -----
(java.sql.SQLException) [DataDirect][SQLServer JDBC Driver][SQLServer]FOR UPDATE cannot be specified on a READ ONLY cursor.

I'm getting the same problem. Did you manage to fix this?

Problem while updating IDOC MATMAS03.

Similar Messages

Maybe you are looking for