MAP change large

Hi,
   when receive or return goods with po, The MAP may change large, system will give a message like "Price change amounting to 42.86 % in month 07/2007".
   I want to know is any parameters to control which percent will show this message? and is there any user exit which i can record the MAP before and after the change?
   we use ECC6.0.
   Thanks in advance.
Lance.

Lance,
- The tolerance key VP (defined for each company code) decides the percentage variance for changes to the MAP of a material during a goods receipt. Typically, this is set to a large value.
- The tolerance keys is defined in transaction OMC0.
- Check out EXIT_SAPMM07M_001 (enhancement MBCF0002) and see if you can capture the current MAP in a Z table before making the good receipt posting.
Hope this helps.
H Narayan

Similar Messages

XSLT Mapping changes Required

Hello Experts,
I got one change requirment, where the name filed in the idoc contains special character (like semi colon) in between the name, I want to put double quotation for that special character at XSLT mapping.
Eg:
Input Name: Ravi ; Kumar
Out put would be: Ravi ";" Kumar
Please help me out with the required mapping changes in XSLT.
Thanks in Advace.
Edited by: ItsUrRock on Mar 23, 2011 11:55 AM

Hi,
use xpath function translate() and escape the semicolon and the quotes.
<output><xsl:value-of select="translate(//Name,%3B,%25%3B%25)"/></output>
If that escapes do not work google for escape sequences.
Regards,
Udo

Mapping changes while upgrading from PI 7.0 to PI 7.31

Hello Experts,
We are upgrading from PI 7.0 EHP 2 to PI 7.31 SP 14 , Dual stack only.
While migration, there are some doubts related with mapping, which are not getting cleared even from going through various blogs like:
Migration Woes?
PI/XI: PI 7.1 upgrade/migration - Message Mappings
Below are my doubts:
As there are mapping changes for IFS, IFSWITHOUT ELSE & Context functions, so exactly what these changes are and how would this work, how can we identify & rectify in all the mappings?
What changes to be performed for Java mapping & XSLT mapping?
Are there any changes for ABAP proxy?
Any help is appreciated
Many Thanks!!!

Hi Lisin,
You need to change in Java mapping accordingly and compile in jre1.6 as many methods used in older version are obsolete now.
You need to write transform instead of execute which was used for PI 7.0
public void transform(TransformationInput in, TransformationOutput out)
throws StreamTransformationException {
You can easily write the code again in message mapping as discussed:
Write Java Mapping directly in ESR!
For XSLT mapping, the older version will be supported as the execution is done using SAP XML Toolkit which is supported in higher versions also.
XSLT Mapping - Managing Services in the Enterprise Services Repository - SAP Library
ABAP proxy will be as it is if you are going for classical scenario as you will be using 7.31 Dual stack.
But if you want to go for AAE Integrated Configuration, you need to do required configuration changes in ECC for outbound Proxy:
Proxy to file scenario using AAE - with full configuration
I am not sure whether you need to change in Graphical standard mapping for those functions which are already there in PI 7.0.
Regards,
Suman

Google Maps have large vertical Stripes.

FF 3.6.12 Google maps have large stripes stating "We are sorry, but we don't have maps at this zoom level for this region." It has stripes of the same width regardless of zoom level. When using Satellite mode, the stripe is replaced with satellite graphic but greatly enlarged.
I have started FF in Safe mode and tried all I can think of. IE shows Google Maps correctly.

You're welcome

IDOC Segment mapping change

Hi,
How can i change the field attached to a IDOC segment.
Actually we have this Invoice IDOC,in which the E1EDK03 012(Qualifier) is passing the IDOC creation date instead of Billing date.
So i need to change this mapping to Billing date.
Please help.

Hi Salz,
I just checked my version of SAP (4.7) and you should get an invoice date. Check out the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC. The first section of this code creates an E1EDK03 segment with the invoice date (if there is an invoice date), with qualifyer 026.
Is there a possibility that in fact you are getting an E1EDK03 segment with the invoice date, but you are also getting other E1EDK03 segments (such as the one you mention with qualifyer 012) and they are obscuring the one you are looking for?
If there are definitely none being created then can I suggest that you debug the subroutine FILL_E1EDK03 in function module IDOC_OUTPUT_INVOIC to check what is happening. You may need to change the timing of your output record to 1 and run the program RSNAST00 online to get the breakpoint to be hit correctly.
If, in your version, the code doesn't include this date, then you have an exit function module EXIT_SAPLVEDF_002 (called via the subroutine CUSTOMER_FUNCTION in function module IDOC_OUTPUT_INVOIC) where you can actually add your own segment data. For example you an change the contents of an existing segment (as per your original request), or append your own E1EDK03 segment with your own data. I would recommend adding your own segment rather than changing whats there.
It is possible to extend idocs to add your own custom segments (eg Z1EDK03), but I wouldn't recommend it in your case, because in later versions of SAP the date is provided and by not creating a new segment (Z1EDK03) you will have no mapping changes to do when you upgrade. You can just delete your userexit code.
Hope that all makes sense and helps you with your problem.
Cheers,
Brad

Unexpected namespace change after mapping change

Unexpected namespace change after mapping change
Posted: Apr 18, 2006 5:17 AM Reply
Hi all
We developped a mapping about one year ago on XI SP9.
The source of the message was an Idoc and the target an XML sample (and not a xsd!) of what our customer expected.
Everything was working fine at that point.
Here is an extract of the output we had:
<?xml version="1.0" encoding="UTF-8" ?>
<env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<env:Header xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd">
<p:sender>
<p:senderId>XXX</p:senderId>
<p:senderName>AUSTRALIA/NEW ZEALAND</p:senderName>
</p:sender>
We are now running SP14 and we had to change the mapping. Since we changed it the namespaces defined in the sample XML we use as a target structure are not used anymore, instead they are replaced by ns0, ns1...
Now the output looks like this:
<?xml version="1.0" encoding="UTF-8" ?>
<ns0:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:ns0="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ns1="http://www.w3.org/2001/XMLSchema-instance" ns1:schemaLocation="http://schemas.xmlsoap.org/soap/envelope/ http://schemas.xmlsoap.org/soap/envelope/">
<ns0:Header>
<ns2:msgDetails xmlns:p="http://localhost/webs/msgDetails.xsd" xmlns:ns2="http://localhost/webs/msgDetails.xsd">
<ns2:sender>
<ns2:senderId>21873</ns2:senderId>
<ns2:senderName>XXX</ns2:senderName>
</ns2:sender>
Any idea what has happened here?
Thanks in advance
Gregory

Hi Gregory,
after a short view I would say that the two structures you have posted are logically equivalent.
I try to make it clear for the sender-element.
In the first example you have a tag <p:sender>. Obviously the namespace prefix 'p' is used here. In order to find out the qualified name of the element represented by that tag you have to find the namespace declaration for prefix p. As the tag itself does not contain such a declaration you have to go to the parent-tag. Indeed, here you find a declaration for p which says that p is just an alias for 'http://localhost/webs/msgDetails.xsd'. Hence the qualified name for the element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Now let us look at the corresponding tag <ns2:sender> in the second document. In oder to identify the qualified name of the element you have to find out, which namespace is bound to the namespace prefix ns2 which has been used here. Again you cannot find this in the tag itself but in its parent. Here you find that ns2 is bound to 'http://localhost/webs/msgDetails.xsd'. (Indeed, here you see that prefix p is also bound to that namespace. This seems to be superfluous to me, as the prefix is never used.)
Consequently, the qualified name of that element is: 'sender' in namespace 'http://localhost/webs/msgDetails.xsd'.
Thus, both tags represent elements with the same qualified name. For more details look at http://www.w3.org/TR/REC-xml-names/.
Greetings Stephan

Locking Map Changes in UpStream 8.3.1

Team - Can anyone let us know how can we LOCK the map changes in UpStream 8.3.1, if this feature is not enabled in this version do we have this in any of the latest versions?
Regards,
Satya

I'm not sure if this is what you are looking to do, but by changing the security level associated with the Update, you can restrict certain users from being able to update the maps. This is really useful for situations where you have a shared parent map used in multiple locations.
So for example, you could set the Update button to require Intermediate-8 access, then make the users Intermediate-9 if they should not be able to make mapping changes.
Hope that helps.

Message mapping changes

Hi All.
I created a message mapping from a custom message type towards MATMAS_BAPI01.
I disabled the EDI_DC40 field and in the idoc communication channel I disabled "Apply control record values from payload".
When I check the final idoc message created, I noticed that some EDI_DC40 parameters were wrong.
<SAP:TABNAM>EDI_DC40</SAP:TABNAM>
<SAP:MANDT>200</SAP:MANDT>
<SAP:DOCREL>640</SAP:DOCREL>
<SAP:DOCNUM>0000000000037246</SAP:DOCNUM>
<SAP:DIRECT>2</SAP:DIRECT>
<SAP:IDOCTYP>MATMAS_BAPI01</SAP:IDOCTYP>
<SAP:CIMTYP />
<SAP:MESTYP>MATMAS_BAPI</SAP:MESTYP>
<SAP:MESCOD />
<SAP:MESFCT />
<SAP:SNDPOR>SAPCX1</SAP:SNDPOR>
<SAP:SNDPRN>host01</SAP:SNDPRN>
<SAP:SNDPRT>LS</SAP:SNDPRT>
<SAP:SNDPFC />
<SAP:RCVPOR>CFDCLNT200</SAP:RCVPOR>
<SAP:RCVPRN>CFDCLNT200</SAP:RCVPRN>
<SAP:RCVPRT>LS</SAP:RCVPRT>
<SAP:RCVPFC />
<SAP:TEST />
<SAP:SERIAL />
<SAP:EXPRSS />
<SAP:STD />
<SAP:STDVRS />
<SAP:STATUS>03</SAP:STATUS>
<SAP:OUTMOD />
<SAP:SNDSAD />
<SAP:SNDLAD />
<SAP:RCVSAD />
<SAP:RCVLAD />
<SAP:STDMES />
<SAP:REFINT />
<SAP:REFGRP />
<SAP:REFMES />
<SAP:CREDAT>2005-09-12</SAP:CREDAT>
<SAP:CRETIM>23:21:31</SAP:CRETIM>
<SAP:ARCKEY>2FE85D8023D311DA9BDB000D56B9D8A6</SAP:ARCKEY> </SAP:IDocOutbound>
In concrete
<SAP:SNDPRN>host01</SAP:SNDPRN> had to be changed into <SAP:SNDPRN>hostXX</SAP:SNDPRN>. I thought the value host01 came from the sld (logical system name of the technical system attached to the business system), so I changed that towards hostXX.
<SAP:RCVPOR>CFDCLNT200</SAP:RCVPOR> had to be changed into <SAP:RCVPOR>SAPCDD</SAP:RCVPOR>. I thought this value came from the rfc destination in the xi sytem, so I created a new one called SAPCDD and configured it into the idoc adapter.
However, this change in the sld/XI system did not affect the generated idoc (no, I did not forget to activate ).
I decided to do some more drastic changes:
- enable EDI_DC40 field in the message mapping
- enable "Apply control record values from payload" in the idoc communication channel
I now hardcode the wanted values.
After activating the changes, still the same idoc is send towards the R/3 system.
Can anyone tell me what I am doing wrong.
Is it a caching problem or am I doing something wrong.
Kind regards

hi Geert,
take a look at my weblog:
/people/michal.krawczyk2/blog/2005/09/01/xi-idoc-adapter--edidc40--demystified
it may answer some of your questions:)
Regards,
michal

ABAP Mapping for Large Messages

Hi Folks,
We are exploring different options for dealing with the fact that XI will choke on very large messages/files. One of the options that we are considering is a third party tool that bypasses XI. However, we've just learned that it may be possible to solve the large message problem by using ABAP Mapping, because supposedly, by doing so, one would bypass the large message being converted to XML as it comes into XI. The scenario involves messages coming into XI on their way to SAP R/3. Does the ABAP Mapping option appear to be viable to you experienced folks out there?
Thanks
Nic

Hey
tunneling as per the term is used mainly for IDOC but we use the term bypass to implement the same concept but with other interfaces.
see if u have simple 1-1 mapping then u can do a bypass scenario in which u are not doing anything in IR,u simple do the configurations in ID.
you can not drastically increase the performance just by choosing some specific mapping.mappin is not made for this .
for best performance you can design a bypass JDBC to IDOC scenario(but then you wont be able to do any message mapping.
have a look at the following for bypass scenario
/people/william.li/blog/2006/09/08/how-to-send-any-data-even-binary-through-xi-without-using-the-integration-repository
if u want to do message mapping then design a JDBC to Proxy scenario.
proxy is mainly used to enhance performance and would be the best bet for u i guess
Thanx
Aamir suhail
Message was edited by:
Aamir Suhail

Mapping of large INVOIC Idocs

Dear SAP,
we have a 1:n mapping scenario.
The source is an INVOIC Idoc that will be splitted into several messages.
The INVOIC IDoc has a sice of 5MB and more than 35.000 data sets.
Because of the huge number of data sets / positions, there are two new
child-segments containing the data sets (see attachment).
INVOIC IDocs with only eg. 100 data sets has noch such child-segments
(see attachments).
In PI message mapping there is an error while mapping large INVOIC IDocs:
While 1:1 mapping of positions (E1EDP01) the text segments
(E1EDPT1/E1EDPT2) are not mapped correctly.
While mapping a position of child-segment ONE the text is mapped from a
position from child-segment TWO.
In our case the 166th position of child-segment ONE is mapped, but the
text is comming from the 166th. position of child-segment TWO.
The text mapping is 1:1. It works without errors while proceeding smaller INVOIC IDocs.
We can´t explain this behaviour.
Also the standard INVOIC structure does not provide such child-segments
while uploading into PI.
Is it a buffer problem in PI?
Is there a maximum number of data records in INVOICE IDocs?
Do we have to adjust the INVOICE structure in PI?
Thanks in advance,
André

Is it a buffer problem in PI?
Could be, but I have used bigger message size without any issues. If your mapping is not too complex, could you write an XSL mapping and check if you run into similar situation? Message mapping has definitely cache issues, hence I prefer XSL.
Is there a maximum number of data records in INVOICE IDocs?
No.
Do we have to adjust the INVOICE structure in PI?
No need to adjust the structure, just try with XSL mapping.

Beat Mapping/Changing Tempo & Maintaining Automation Timing

If you've ever changed the tempo in a song (beat mapping or other kind of re-clocking), you probably know that it's extremely important to SMPTE-lock your regions before attemping those operation (this way you can adjust the tempo/metronome to conform to real-time performaces not done to a click, etc. etc. etc. without affecting/changing the relative positions of regions/notes/events).
The problem with these kinds of operations is that changing the tempo after automation has been written totally screws up the timing of the automation moves, because the spacing between individual automation events will move according to the changes you make to the tempo.
So... the solution I've come up with is to not only lock regions prior to beat mapping/reclocking, but to also lock the automation data. This is accomplished in the automation arrange page (details below). Once you're done with your beat mapping/reclocking/tempo changing, re-open the automation arrange page and un-lock the automation regions.
So far this seems to work like a charm. Here's how you do it:
Assign a key command to open the automation event editor (on any track that contains automation). Hit CMD-1 to open the automation arrange window, CMD-A, and then SMPTE-lock. (having SMPTE-lock on a key command is very handy).
To unlock the automation data, follow the same procedure, except this time CMD-A and un-SMPTE-lock the regions (also handy to have on a key command).

Nice tip, Los Schwartzos!

OWB won't take mapping changes on first attempt

Hello,
Here is my problem: mapping that was previously validated, deployed and executed successfully requires a minor change. As an example, let's say, I want to change the default value of the column in "Key Lookup" object: from default null to 0. I clearly apply this change, then validate my mapping again, then go to the "Deployment Manager", re-deploy the mapping (with option "replace") and execute. When I verify the execution result - the change I've applied to the mapping was NOT taken. When I do the same second time, it does go thru successfully. I ran into this problem many times - the first attempt to make changes to the mapping almost never goes thru. I had to do it twice on regular bases.
I'm wondering if anyone has been thru the same problem? Am I doing something wrong?
The version of OWB is 10.1.0.1.0, the database is 9iR2 (9.2.0.7)
Thanks for help.
vr

This is a quirk with OWB that I've grown accustomed to. It seems like sometimes if you make a change to an operator, it doesn't save it. I usually double-check my changes before deploying.
If I make a big change to an expression, I'll copy it to the clipboard, leave the expression editor, then open it back up to check it. If I lost the change, I'll paste it back in, then do it again. For some reason, it always seems to work on the second try.
I am using an older version of OWB (9.2.0.8, I think).

Editing and changing large text file

hi,
new to this, so bare with me.
got a large text file 44meg and i need to change some values in it.
example:
TSX ;20030102;40302216;40300579;1980;1900;3762000
i need to change the lines so that they read:
TSX ;20030102;302216;300579;1980;1900;3762000
thus removing the leading 40 in the middle cols.
Thanks in advance
john

crap, small mistake
1) use BufferedReader to read in the file line by line (BufferedReader.readLine())
2a) for each line, split it on the semicolons (String.split())
2b) change the middle value using String.substring()
2c) construct a new line by appending all strings in the array returned by 2a) to eachother
2d) write this new line to a file using PrintStream (PrintSteam.println())
3) when done, close both the reader and the printstream.

Import and Syndication maps - change in XSD

HI All,
Can any one let me know are these are correct if it is then are there any work around solutions?
We created manually Import and syndication maps.. fine..After few days we changed data type/deleted the filed/added new fields.... In all these above incidents do we need to recreate import and syndication maps????
There is no other work around for this ??
2) Even if there is no change in Repository structure but change in import or syndication XSD do we need to recreate all import and syndication maps???
Your inputs are really helpful.
Thanks
Rajeev

HI Rajeev,
So for any change in the MDM repository Import maps and syndication maps are not needed to recreate from scrach right?
For minor changes like field add there is no need.For changes involving deletion of mapped fields,changing types of already mapped fields,deleting mapped tables,one should first unmap the current map and then carry out structural changes.Later one can remap them again,this is to avoid maps from getting corrupt.
If there is any change in the XSD then there is a possibility to recreate the map from scrach??
Yes
Do Update XML schema option avaliable only in MDM 7.1?? not in 5.5?
Yes
A good description and usage is given by Aamir here Update of XML syndication map when XSD is changed
One more thing want to clear : I created a scheme and assigned the XSD.. Now when I created the port I am unable to assing the schema like I do for import map??? then what is the use of XSD schema for outbbound??
Seems you are not using in the way it is supposed to.the exact usage and defining what feature is available with which port is mentioned in pg no 356 of Console guide.
What is the usual method of import XSD and Outbound XSD?? Do Source and Target systems provide XSDs to MDM or MDM provides to Source and Target Systems?
For Standard contents SAP provides ready made xsds.
It is important to note that xsds are only to make MDM and other system understand the xml so they should be same.
To do this you can use Altova tool to create xsds based on your xml,also PI can help you do the same.
You can create xsd with PI for other idoc type too.
Hope this helps.
Thanks,
Ravi

How to track OWB mapping changes?

Hi,
I'm a new bee to OWB. And I have a scenario where in more than one person will work on the same mapping. so I dont see any way to track the changes made by others. Is there a way to track who updated the OWB mapping last time and the changes they have done on the mapping??
Any help is Appreciated.
Thanks!!

I don't think there is a good way to track details for changes. There is a snapshot feature, but I don't think you can see what the specific modifications were. I don't use it. I use periodic mdl backups in case I need to recover the design (fortunately never had to do it) or to move updated objects across (when needed I track which objects changed in a spreadsheet). I also use a fairly primitve way of tracking my changes by storing prior versions of mappings (not all). If I want to keep a prior version, I copy the mapping and add '_V#' at the end. This indicates my last prior version. Then if I want to create another copy I will rename the current '_V#' to '_V1' (i.e. '_Vn'). Next I will create a copy of the current mapping and add the '_V#' at the end. Nothing sophisticated, but I use this sometimes and cleanup as things progress.
If there is a way to track and see all detail changes I would love to hear about it also.
Thanks!

MAP change large

Similar Messages

Maybe you are looking for