Idoc CREMAS.CREMAS04 in update mode

Hi,
I have some vendors who are already created in my ECC, and I must to update some fields of his basic data by using an inbound IDoc (sent by XI).
My question is: is it possible to CHANGE only ONE value (e.g NAME1) without to give all mandatory fields (like Account group, city, zipcode) ?
My idoc is CREMAS.CREMAS04.
In my IDoc segment, I use option E1LFA1M-MSGFN = 004 (change)
In my partner profile, I use "CRE1" for process code.
Regards.
Mickael

Hello Mickael,
I have the same issue. I would like to import from Legacy some data but I also DON'T want to update one field. How to you set it as exception for not updating the supplier please?
Thanks in advance,
Génia.

Similar Messages

Segment E1PITYP occurs for each subtype of Infotype 1001 in update mode

Hi,
I am using transaction PFAL and IDoc HRMD_A for transferring HR data.
In update mode the resulting IDoc contains segment E1PITYP for each subtyp (for example A002) of Infotype 1001 even if it contains no segments of type E1P1001.
Could somebody explain this and is it possible to avoid this behavior?
Thanks and regards
Patrick

Hi,
thanks for your answer.
Still I am little bit confused and want give an more detailed description of my problem.
If I export an organizational unit in initial mode I have for example 5 segments of type E1PITYP and each of them has a subsegment (for example E1P1001).
Export of the same organizational unit in update mode results in more than 200 segments of type E1PITYP and all of them without subsegment.
This seems to happen for all infotypes (not only 1001 like I thought before).
Now I want to understand why this happens and if it's possible to update an organizational unit without segments of type E1PITYP that don't have a subsegment.
Regards
Patrick

I want IDOC for Vendor master updation ( XK01 &XK02 )

Hi
I want to do LSMW in IDOC method for this vendor updation.
So I want IDOC for Vendor master updation ( XK01 & XK02 ).
I want to do both create vendor and change also.
Regards,
Ravi
Edited by: kandukuri ravi on Dec 1, 2008 2:56 PM

Hi,
For Vendor Master using IDoc's for LSMW,Use Message Type = CREMAS and Basic Type = CREMAS05.
For Basic type 01,02,03...05 are versions which includes more fields in basic type so better use latest version.
Hope it will help you.
Regards,
Sudhakar Reddy.A

Segment E1PITYP occurs for each subtype of infotypes in update mode

Hi experts,
In update mode the resulting IDoc contains segment E1PITYP for each subtype (for example 7) of Infotype 6 (for example) even if it contains no segments of type E1P1001.
I can see all infotypes and subtypes of the distribution model in the idocs. Even if the employee does not have an infotype or one specific subtype. In this case, node E1PITYP appears without child node.
Thanks a lot for your help
Cheers,
AS

Hi,
thanks for your answer.
Still I am little bit confused and want give an more detailed description of my problem.
If I export an organizational unit in initial mode I have for example 5 segments of type E1PITYP and each of them has a subsegment (for example E1P1001).
Export of the same organizational unit in update mode results in more than 200 segments of type E1PITYP and all of them without subsegment.
This seems to happen for all infotypes (not only 1001 like I thought before).
Now I want to understand why this happens and if it's possible to update an organizational unit without segments of type E1PITYP that don't have a subsegment.
Regards
Patrick

HRMD_A Delimiting Date Update Mode

Hello all,
For creating a Employ master i have used HRMD_A IDOC.It is successfully creating it.
But when i try to Update the Employ Master :
         For creating the existing infotype with the new evaluation period.It is overwriting the existing record.
Ex : For an Employee XXX , 07 infotype already exists with valid period as 12.01.2001 to 31.12.9999
When iam running in update mode (OPERA : U)
          --With changed data & with new valid period 3.02.2001 to 31.12.9999
         --- Ideally it should delimit the existing record from 12.01.2001 to 2.02.2001
         -- But when process the IDOC it is Overwriting the existing record.History is getting deleted.
Is there anything iam missing while passing the data.
How to resolve this issue ?
Regards
Prasad

Hello, we have a scenario identical to the one described in the original post. We are using HRMD_A07 with process code HRMD. Does anyone know of a solution to delimit the historical records? Is this functionality dictated by the process code?
Thank you,
Brian

IDOC CREMAS - withholding tax

Hi Experts,
i need to distribute idoc CREMAS with data related to "withholding tax"
(table LFBW).
When i distribute this idoc i can not see these data in outbound, do you know if i need to do something special to aktivate this part? and do you know what is the segment related?
how can i send these data with the whole IDOC CREMAS?
Thanks for your help
Boris

Hi lakshimiraj
I'm sorry but i never fix this issue becouse the process was changed and no need to distribute whitholding tax.
Any way i think you are right, you need to exted IDOC creams with custom segment then you will update the new segment in outbound and in inbound you need to update the new fields.
You can try maybe with these exit EXIT_SAPLKD02_001 (ENHANCEMENT VSV00001)
good luck
Boris

IDOC CREMAS

Hello,
i need to replicate idoc CREMAS to another R3 System, the idoc is triggered correctly but it contain only segment E1LFA1M and i need also the segment to update table LFB1 (company) E1LFB1M plus all other segments .
i can not understand why.
any Idea??
Cheers Boris

Issue fix!!
(wrong userexit was implemented)

LSMW, CREMAS04, and updating Partner Functions

I am involved with converting legacy data into SAP. To populate the SAP Vendor Master correctly will involve 3 passes using LSMW:
Pass #1: use IDOC CREMAS04 and populate the majority of master record fields
Pass #2: use BAPI: Business Object "BUS4001"; Method "SAVEREPLICA"; Message Type "ADRMAS"; Basic Type "ADRMAS03" to update Vendor record address data.
Pass #3: use IDOC CREMAS04 and update Head Office, Alternate Payee, and related Partner Function data.
The problem I am having is best explained using the following example:
When a vendor record (ex: Vendor Number 300004) is first created, the following 3 Partner Functions are also created automatically to reference the same vendor number: OA, VN, & PI (Ordering Address, Vendor, & Invoicing Party):
OA    Ordering Address    300004   Vendor A
VN    Vendor                   300004   Vendor A
PI      Invoicing Party        300004   Vendor A
This particular vendor is actually one of many "plants" or "warehouses" of a larger vendor, and I need to configure the record to reflect that the Purchase Orders go to the Parent Vendor (Head office) and that the Invoice comes from the same source. Therefore, I need to remove or edit the existing OA and PI partner functions so that I only end up with the same 3 Partner Functions, but the linked vendor record for partner functions OA and PI needs to be that of Head Office.
Example: if using Vendor Number 300005 "Head Office Vendor"
OA    Ordering Address    300005   Vendor A
VN    Vendor                   300004   Vendor A
PI      Invoicing Party        300005   Vendor A
What I am actually seeing when I post the IDOC is the following:
OA    Ordering Address    300004   Vendor A
OA    Ordering Address    300005   Vendor A
VN    Vendor                   300004   Vendor A
PI      Invoicing Party        300004   Vendor A
PI      Invoicing Party        300005   Vendor A
Can anyone shed some light on this?

Don,
I am trying to work with the same data that you discussed in this thread. Can you send me some additional details on your Pass #2? I was successful in Pass #1, particularly in adding new PI vendors when necessary and deleting the existing internally created PI vendors. But I'm stuck on Pass #2 where I want to add the extended address information that you mention using the SAVEREPLICA BAPI. I can certainly use the recording method, but would like to leverage the power of the BAPI approach.
Thanks in advance!
Wes

Error in IDOC CREMAS for Bank data

Hi,
I am trying to upload vendor master through IDOC.I am also sending bank data in my IDOC.But it gives the below error
Fill all required fields SAPLBANK 0100 BNKA-BANKA
We have created the bank and details exist for that bank.
We are giving Bank Country Key,BANKKEY and BANKACCOUNTNUMBER details in IDOC.
When I have Reprocessed the IDOC thru WE19 in Foreground mode It goes to bank screen twice.First time the okcode is 06 and second time the okcode is 16 which take the control to other screen where it ask bank name.But Bank name already exist for that bank.we are not giving bankname from the idoc.
Any help appericiated.
Thanx.
Rekha.

Sidenote because this thread is one of the first results in google when searching for "SAPLBANK 0100 BNKA-BANKA":
Please have a look at [SAP OSS Note : 697492 ALE: Bank master data updated - DEBMAS|http://www.google.de/url?sa=t&rct=j&q=sap%20oss%20note%20%3A%20697492%20ale%3A%20bank%20master%20data%20updated%20-%20debmas%20&source=web&cd=1&ved=0CB4QFjAA&url=http%3A%2F%2Fforums.sdn.sap.com%/community [original link is broken]%3FthreadID%3D2047770&ei=PDbWTv6OK4eJhQeY2tlZ&usg=AFQjCNGnp_ieUhM9jNZi9Rd-s-N9i1FNpw&sig2=pmD56XZs_GAtNI3zMsJPLw&cad=rja]
Regards
Martin

Lock records when in Update Mode / problem with 2 users on 1 document

Hi,
when user A updates e.g. a purchase order and user B goes into this purchase order and updates e.g. the remark before user A, then user A cannot save his changes. Imagine user A has put in several new lines and has made several price adjustments, his work will be gone.
In most cases this should not happen very often, but it could. Since B1 recognizes when another user has updated the document before, it should be possible to solve this situation more convenient (either by lock, saving to a new document, comparing to the old version, etc).
Thank you
Sebastian

Hi Sebastian,
Your request is understandable. It may not have big problem to change current process by coding. However to lock records whenever in update mode, that could create too many locks. It is basically not good for performance. The trade off may be allowing save as function. However, this may not be a desirable solution for most end users.
Thanks,
Gordon

Master Data loading got failed: error "Update mode R is not supported by th

Hello Experts,
I use to load master data for 0Customer_Attr though daily process chain, it was running successfully.
For last 2 days master data loading for 0Customer_Attr got failed and it gives following error message:
"Update mode R is not supported by the extraction API"
Can anyone tell me what is that error for? how to resolve this issue?
Regards,
Nirav

Hi
Update mode R error will come in the below case
You are running a delta (for master data) which afils due to some error. to resolve that error, you make the load red and try to repeat the load.
This time the load will fail with update mode R.
As repeat delta is not supported.
So, now, the only thing you can do is to reinit the delta(as told in above posts) and then you can proceed. The earlier problem has nothing to do with update mode R.
example your fiorst delta failed with replication issue.
only replicating and repeaing will not solve the update mode R.
you will have to do both replication of the data source and re-int for the update mode R.
One more thing I would like to add is.
If the the delat which failed with error the first time(not update mode R), then
you have to do init with data transfer
if it failed without picking any records,
then do init without data transfer.
Hope this helps
Regards
Shilpa
Edited by: Shilpa Vinayak on Oct 14, 2008 12:48 PM

ERROR: Update mode C is not supported by the extraction API - R3 11

Hi gurus,
I just tryed to implement the solution I found at this link:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/d3219af2-0c01-0010-71ac-dbb4356cf4bf
The data source is based on an Infoset on the KONV R/3 Table.
I setted the AIM delta process and I did all the activities as written in the document.
The process works if I load data to bw in "full", with "Init without data transfer" and "delta" mode. Of course if I change a Purchase document, it will be posted in the delta queue and then loaded to bw with the next delta load.
The "initialize delta process" (with data) doesen't work and returns the following error:
Update mode C is not supported by the extraction API
the error code is R3 11.
have you any idea about it???
Thanks!!!
Regards!
Matteo

Hi,
for me it sounds quite simple. It is that the update mode 'C' get flagged as 'not allowed' for this extractor. Did you check with rsa3? I guess you will get the same error message. May be you can start debugging in rsa3 to find the place where the update mode gets checked.
Anyway, it shouldn't be a issue as you have a workaround. May be you should raise a error message at sap because of this.
regards
Siggi

How to use a single page for create and update mode.

Hi,
I need to develop a single page to be used for both create and update modes.
I am going to use a variable MODE
and i will set this in the emp summary page.
Based on the button clicked by the user i have to render the JSF page.
For tis if the user selects a perticular and cliks on update thn i will pass the empno to the next.
so there in the next i will appy a ViewCreiteria on my View Obj to fetch only that row so that only that emp will be displayed ion update mode.
This is working fione for me.
So now the issue is
when the user clicks on CreatEmp button.
i need to enable my VO for insert operations.
for this i wrote the code like this in the beforePhase event
FacesContext ctx = FacesContext.getCurrentInstance();
ValueBinding valBinding = ctx.getApplication().createValueBinding("#{data}");
BindingContext bContext = (BindingContext) valBinding.getValue(ctx);
DCDataControl dcControl = bContext.findDataControl("DataControl");
Application app = ctx.getApplication();
ApplicationModule am = (ApplicationModule) dcControl.getDataProvider();
System.out.println("After Appmodule initiation");
// get the VO reference and initiate the query
System.out.println("Before Page VO initiation");
PrismDmPageSectionViewImpl vo = (ViewImpl)am.findViewObject("View");
//ViewRowImpl row = (ViewRowImpl) vo.createRow();
/* TO CREATE AN EMPTY ROW*/
Row row=vo.createRow();
System.out.println("New Row is created");
//vo.createKey(row);
vo.insertRow(row);
vo.setCurrentRow(row);
By doing this a new empty page is rendered.
But when i fill up the values and click on ok.. i am getting the error like this..
JBO-27023: Failed to validate all rows in a transaction.
JBO-27027: Missing mandatory attributes for a row with key null of type View3
JBO-27014: Attribute Id in View3 is required
JBO-27014: Attribute PageeId in View3 is required
Please point me out where i am missing.
Thanks

Hi,
In my opinion you are over complicating things.
This is what I do for using the sme page as both create and update without all this code.
1) Create a browse page containing a an adf table with a select one component bound to your view object.
2) Create an additional edit page containing only an edit form containing fields of your view object that your users must enter in order to add or edit rows.
3) Link the pages in the JSF diagram with an "edit" navigation case from browse to edit page and a "return" navigation case from edit to browse (make sure that redirect option is NOT set on both cases)
4) Remove the submit button from the edit page and add two application module bindings for the commit and rollback operations as command buttons in the form footer facet. Make sure that both buttons has an action of return and that their disabled property is set to false. You will probably change their labels to ok and cancel respectively.
5) Drop a create action for your view object from the data control palette inside your page as a command button and set the action property to edit also.
3) Set the action property of the view button to edit
This should basically work without any code from your part. -- at least it does so for me -- if you like to make it a bit more funcy you may add am action listener inside your buttons and set a requeScope variable for example #{requestScope.editing} to true or false depending on the button clicked. Then add a title to your page with a value like #{requestScope.editing == true ? 'Editing record' : 'Adding a new record'}..
Hope that helps.
Thanassis

Changing update mode in Error DTP

Hi Gurus,
I have some issues with data in PSA. I am trying to solve it using Error DTP.
While Executing DTP one record failed to load giving bad request. Now i created an error DTP. By default the extraction mode is Delta.
DTP extraction Mode->Full
Error DTP Extraction Mode -> Delta; How can i make it full. If i amm trying to change it, The option is disabled.
Thanks in advance!
Regards
Anu

Hi Anu,
In my system original DTP is full and when i create error DTP, i got error DTP extraction mode is full.
Yes you are right, it is disabled.can you check the update mode of your original DTP once.
once the error DTP is created, we can not change the update of it.
Regards,
Venkatesh.

I have updated to IOS 6, the App store won't work, is stuck in update mode for 1 day and the battery now goes flat in 3 hrs without use. Can I go back to IOS 5?

Hi, I was forced to upgrade to IOS 6 due to a restore.
Since the upgrade, I have lost information, the App store is stuck in update mode, my battery drains in hours and many more problems.
Is there a way to go back to the VERY RELIABLE IOS 5? This phone is nearly useless now.
Thanks

Just FYI - the situation is resolved. I downloaded the new snow leopard 10.6.8 update for safari and now itunes works. I have no idea what that has to do with anything - but I saw it on another forum and it actually worked.

Idoc CREMAS.CREMAS04 in update mode

Similar Messages

Maybe you are looking for