Error Propagation on a 2 way receive port

HI,
we have a 2 way receive port . The subscribing send port makes a web service call to a third party and the received response
goes back to the client via the received port.
All good if things are working! In case of any exception on the send port side, is it possible to propagate this exception to the client? any way to achieve this? Basically I want the client to be notified of any exception that occurs in the chain.
Please suggest.
thanks
MS

Hi MS,
All you need go do is enable "Propagate Fault Message".
Following the exact extract from MSDN on this context: "For the two-way send port, you can choose whether to forward SOAP fault messages on to the original caller
over a solicit-response send port by selecting Propagate fault message. If this option is not selected, BizTalk Server will generate a NACK first, and then suspend the message. If it is selected, BizTalk Server will treat
the message as a valid WCF response message from the external service and the response message will not be suspended because it is propagated."
If you need to handle this
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Similar Messages

Receiver port missing in inbound idoc

Hi All,
I am posting idocs from XI to R/3. All the ALE settings have been done correctly. Idocs were being posted to R/3 successfully, however suddenly the idocs started failing in R/3 with error: EDI: Partner profile inbound not available
When i checked the control record for the errored idocs i found that the receiver port is missing. I am not sure why this is happening as in the idoc adapter we have provided this and also the idocs were being posted successfully with the same setting.
Pls help to find the root cause for this problem.
Further what would be the best way to reprocess these failed idocs? The number is huge around - 30,000 hence manual processing through we19 is not possible. Also BD87 cannot be used as i need to edit the idoc to add the receiver port information before reprocessing.
Kindly suggest. Any help in this regards would be welcome.
Thanks
Anand Chavan

hi
Go thru the below blogs
check the partner profile settings
http://help.sap.com/saphelp_nw04/helpdata/en/dc/6b80b543d711d1893e0000e8323c4f/frameset.htm
Idocu2019s not posted in the receiver SAP Systemsu2026.
/people/sravya.talanki2/blog/2005/10/27/idoc146s-not-reaching-xi133-not-posted-in-the-receiver-sap-systems133
Troubleshooting File-to-IDOC Scenario in XI.
Troubleshooting File-to-IDOC Scenario in XI.
reward points if helpfull
regards
kummari

"Receiver port not valid in control record"...idoc error

Hi,
The new materials are sent to SAP via a text file which is placed in the application server which EDI uses to populate the Idoc segments and creates the material master.
Recently we upgraded from SAP 4.6 C to ERP 5.0.
After upgrading we are getting a message as Port(HPLED) invalid in control record.
I get an error message as "receiver port HPLED not valid in control record"...
It is not able to find the receiver port & hence cannot create the MM.
We checked all the config and compared with Test and production and we could not find any noticable change.
Did anyone come across any infor on this?
Your valubale reply is really very important for me.
Pls reply.
Regards,
Pri

Hey Ramesh,
I've already done the WE57 setting.
You see the WE57 setting is always done on the reciever side and not on the sender side (There is no harm but it is not what SAP recomends) The Linking on the sender side is done in the Partner Profile, where we give the extension name.
For the reciever this Partner profile setting of extension is not there therefore we need to go to WE57 and do it.
I've done all the config and have tried all the things in both the systems but somehow nothing is working.
That is why I asked that in my Inbound FM which is IDOC_INPUT_HRMD do I need to popluate one of it Parameters or fields where I mention the Extension name and all.
Yesterday however I found an SAP NOTE (105148) which tells me that my naming convention of the Extension is wrong. I have made ZHRMD_A07 extending standard IDOC tupe HRMD_A07, actually it should be ZRMD_A07. Again this is speculative I need to try this out. But I do know that SAP has various checks which checks all the naming convention and all. I'll try this out and hopefully it might work.
In the meantime any other suggestions are most invited. I am using Message type HRMD_A and using IDOC type HRM_A07
Regards
Abhishek Sahi

Getting error - A message going to a one-way send port is being suspended.

Hi,
I am getting the following error message (in the BizTalk administration console), on my Production servers, upon testing one of my BizTalk Interfaces, deployed on the same :-
A message going to a one-way send port is being suspended. Reason: The send port configuration corresponding to the message was not found.
This usually happens when a send port was deleted while it still had some active messages.
The same application is working fine on the Test environment.
Please note
à This is a clustered BizTalk environment.
I have checked, both the Host Instances are running properly, on the same environment.
I am also able to connect to the SQL database (Msgbox) server, that the BizTalk servers are pointing to.
Can you kindly guide on the same.

Hi Shalini,
This very well could be an SSO issue. Are you getting any SSO errors in the event log? Intermittent SSO issues could cause the
inconsistent results you are seeing.
Of course, as the port configuration is stored in the SSODB, if access to this database is restricted port configuration cannot be accessed
and so the message could not be delivered.
Refer: http://blog.sabratech.co.uk/2007/02/send-port-configuration-corresponding.html
Also, try changing the send handler to run under different host instance.
Rachit
Please mark as answer or vote as helpful if my reply does

Error propagating servlet user to peer?

Hello,
We currently have a Windows 2003 Server 32bit running ColdFusion 8.01 with 3 instances named: cfusion, Instance1 and Instance2. Instance 1 and Instance 2 are clustered together and serving all our sites in IIS. We're hosting just over 200 sites with approx. 6-7 hits a second.
ColdFusion is running with all the latest hot fixes and patches. The JVM is version 1.6_24.
For a while now one of the instances in the cluster randomly locks up a few times a month, fails to return pages and has high cpu usage. We'd normally just restart the instance and things would return to normal. It's bad to ignore things but it's only recently I've had a chance to look into the cause of these lock ups.
Last night both the instances appeared to fail. We have an external monitor that hits our sites every 5 minutes to ensure they are still running.
Scanning through the JRun logs at about the time we received our first monitor warning there are a bunch of what appear to be propagation errors on both instances.
Logs from Instance1:
22/03 07:10:14 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:16 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:17 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:18 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:20 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:21 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:23 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:23 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:24 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:24 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:25 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:26 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:27 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:28 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:28 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:10:29 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketTimeoutException: Read timed out
22/03 07:17:43 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
Logs from Instance2:
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:40 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset by peer: socket write error
22/03 07:10:41 info Clusterable service JRunRMIBroker discovered ClusterManager on xxx.xxx.xxx.xxx:3862, cluster domain: cluster1 (Lookup Service's JINI-ID: xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx)
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.io.EOFException
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.net.SocketException: Connection reset
22/03 07:10:42 warning Error propagating servlet user to peer: error during JRMP connection establishment; nested exception is:
    java.io.EOFException
22/03 07:10:43 error ROOT CAUSE:
java.lang.OutOfMemoryError: unable to create new native thread
    at java.lang.Thread.start0(Native Method)
    at java.lang.Thread.start(Thread.java:640)
I suspect it's a JVM memory issue, however I have no way of extracting or creating memory logs without bringing all our sites down again.
I only know the basics of how the JVM heap space works but my guess is that one of the instances can't create any more threads because the PermGen space has run out and it's killing the cluster.
Here's our current JVM settings: java.args=-server -Xmx768m -Xms768m -Dsun.io.useCanonCaches=false -XX:MaxPermSize=192m -XX:+UseParallelGC -Dcoldfusion.fckupload=true -Dcoldfusion.rootDir={application.home}/
Has anyone come across this issue before or has any ideas on how to better debug the issue with minimal impact on uptime?

Well the classes should be in WEB-INF/classes, but I don't think that's your problem.
Getting an applet to connect to a db is notoriously difficult (so I've heard - I've never tried it), so having the applet talk to the servlet with the servlet in turn talking to the db is a good idea.
"i cant see the error message because it wont print in the VM,"
That doesn't sound right. What does your error handling code look like?
" MySQL it also has access permissions for some weird reason."
MySQL is set up so that user credentials are only valid from a specific host unless you explicitly tell it that a user can connect from anywhere. This is native to MySQL and has nothing to do with java or JDBC.
Most of the code you posted throws Exceptions. Are you catching them, and if so what did they say?

How to creat a numerical error propagation program

trying to create a numerical error propagation program

The response 'we have your suggestion on file' is typical. Let's look at the history, although it may be brief here. I suggested this almost a year ago. Others in this thread, although they may have a different purpose, asked about this capability 5 years ago.
At the same time, LabVIEW adopts 'upgrades' every six months that, from my perspective, seem more as a mechanism to force users to the new products. Many of the upgrades take LabVIEW in new directions and can be interesting at a more advanced level, but in the instruction of undergraduate engineering students, this has little purpose. I don't want upgrades that cause me to change the LabVIEW lesson plans I have developed even though the changes are mostly superficial things like labels and where objects are located on menus. A frustrating thing is that lab manuals are developed and printed (on paper) ahead of a course with directions for the 'old' version and then an upgrade happens that might create differences in the software, making the lab manual's directions 'wrong.' With constant hardware, what we do in the laboratory does not change much and the software has to do a basic job of consistenty supporting the DAQ hardware's functions. If the changes in LabVIEW versions become too great, our curriculum will switch over completely to MATLAB and use a fixed basis of hardware drivers. In MATLAB, with its matrix formats, the error analysis is relatively easy to do and the plotting capabilities are superior.
The paradox for me is that I want upgrades, but upgrades that add capability to the LabVIEW without changing the functions that already work. One of the desired upgrades is a new datatype for error analysis using duals, with a new wire color to respect the processing mathematics and provide support for error analysis. Here I mean error as component of 'uncertainty' and 'error analysis' including the two main topics of 'error sources' and 'error propagation'. These are important subjects in the undergraduate engineering curriculum and many research publications require the reporting of uncertainty. Upgrading from v7 to v8.2, we saw that the 'LabVIEW people' thought it important enough to make the error datatype (execution errors) its own wire color and datatype as a distinct cluster (this 'dark yellow' appears as more an olive color) to replace the error stream's pink color of mixed datatype clusters. From a user's perspective, error analysis of the measurement is important and should have its own datatype and wire color too.
Yes, there are ways in LabVIEW 8.2. (and probably later versions) to develop a new wire color and datatype but there is significant overhead using projects and classes. The questions for me, as an instructor of lab courses, are how much of this needs to be taught to the students and will the learning of LabVIEW to perform DAQ become too complicated if projects and classes must be understood? Digging down into the VI, sub-VI and function hierarchy levels, there has to be a balance struck between 'need-to-know' and 'don't go there'. The projects and classes go up in level, placing VI's in a larger structure but we still must ask if this is 'need-to-know.' If LabVIEW pursues this proposal of a new datatype and wire color for duals, this error analysis method would be placed on the current level of LabVIEW and we would not need to address different levels or ask if it is 'need-to-know.' It becomes more functional and serves the user in providing simultaneous error calculations and a basis for uncertainty reporting.

Realignment showing multilevel error propagation carried out and

While executing realignment table it is showing following :-
Realignment showing multilevel error propagation carried out
Realignment of live cache time series aborted
Have seen all consistency checks and everything is fine no alerts received.
Please suggest
vikas

Hi Vikas,
I am assuming that you have maintained the Realignment table properly meaning you have only the necessary entries and removed all unwanted entries. Having assumed that the other reason why this error can come up is when you try to realign more than 1 Characteristic Value in the same table entry.
For Example.
Let us you have 3 Characterstics viz, product, location,customer.
If for Product P1, you are trying to change the location from L1 to L2 and customer from C1 to C2 then there is a possibility such an error might occure.
In such cases we need to create 2 entries as follows
1) P1 L1 C1 to P1 L2 C1
2) P1 L2 C1 to P1 L2 C2.
It is better to avoid Multiple characteristic changes in a single step.
Hope this helps.
Thanks
Mani

IDOC ( WS-- XI -- R/3) Receiver Port

Hello i am having issues with IDOC post on R/3 via XI. The issue is with receiver port. I am populating values of Message variant and message function in Mapping and nothing else were populated.
As per SAP documentation RCVPOR variable will be populated from receiver adapter whether "Apply control record from payload is checked or not".
This value RCVPOR is being populated control record of idoc when "Apply control record from payload" is unchecked . when its checked its not . please comment

Hi Bujji,
did you see the RCVPOR in your payload?? if yes then select all the three check boxes in adapter refers to payload.
basically there are two ways to send Receiver and Sender details to R/3, one is from payload and the other is from configuration.
if you check the "Apply Control record from payload"
along with this you shd check "Take Sender from payload" and "Take Reciever from payload". then it should work.
if you uncheck Apply control record from payload then it will take these details from SLD. Make sure that these are given there.
Regards,
Sukarna

Best Way to port the data from one DB to another DB using Biztalk

Hi,
please suggest best way to move the data from one db to another DB using biztalk.
Currently I am doing like that, for each transaction(getting from different source tables) through receive port, and do some mapping (some custom logic for data mapping), then insert to target normalized tables(multiple tables) and back to update the status
of transaction in source table in sourceDB. It is processing one by one.
How/best we we can do it using bulk transfer and update the status. Since it has more than 10000 transaction per call.
Thanks,
Vinoth

Hi Vinoth,
For SQL Bulk inserts you can always use SQL Bulk Load
adapter.
http://www.biztalkgurus.com/biztalk_server/biztalk_blogs/b/biztalksyn/archive/2005/10/23/processing-a-large-flat-file-message-with-biztalk-and-the-sqlbulkinsert-adapter.aspx
However, even though a SQL Bulk Load adapter can efficiently insert a large amount of data into SQL you are still stuck with the issues of transmitting the
MessageBox database and the memory issues of dealing with really large messages.
I would personally suggest you to use SSIS, as you have mentioned that records have to be processed in specific time of day as opposed to when the
records are available.
Please refer to this link to get more information about SSIS: http://msdn.microsoft.com/en-us/library/ms141026.aspx
If you have any more questions related to SSIS, please ask it in
SSIS
forum and you will get specific support.
Rachit

EDI: Receiver port in control record is invalid

Yesterday, we got refreshed out quality system with the production SAP system.
I am trying to process IDoc # QXXXXXXX in quality but I am getting the following error message:
EDI: Receiver port in control record is invalid.
To create this IDoc, I copied IDoc # PXXXXXXX using WE19 and modified certain fields so that it would change the clearance status. The IDoc I used to copy from was from production server and a part of the recent refresh of Production serveru2026
could that be the reason that the EDI Receiver port is invalid or is there another reason?
THANKS IN ADVANCE.

Hi sam kumar
Ports and Partner Profile may be Same or Different in Quality and Production systems.- it is Client dependent
U can cross check Ports using WE21 with Quality system and production systems
U can cross check Partner Profile using WE20 with Quality system and production systems
if both are not same u need maintain port and partner profiel before creating idoc using we19...
Note: Keep a note on Logical system also..
I hope this help for all when system refreshs,.
Ramesh

Problem with distribution model receiver ports

Hi,
I am facing a problem with distribution model.
I am using Distribution model for material classification data. I am sending my classification data using CLFMAS message type to one of the receiver. Again another person also sending classification data to another receiver.
But both objects will run at different times.
Problem is for every run and every change it is creating 2 idocs instead of 1 idoc.
I am able to create an IDOC with my changes for classifications. But it is creating 2 idocu2019s instead of creating 1 idoc. Because of there is another distribution model with same message type with different receiver port has been configured. I.e. reason it is creating 2 idocu2019s and sending to both the revivers.
When I run my changes It needs to create 1 idoc and send to my receiver port. If another person run his job it needs to create another idoc.
So how will I filter distribution model based on receiver port? it needs to create only 1 IDOC ..

Hi kotesh,
A similar issue.
check if this will help.
Do the following:
Go to TOOLS>ALE Development>IDoc Type Development> WE81 and create a new message type and give it a different name - say ORDERS2. Use WE82 to link it to an IDoc Type - say ORDERS05. So now you will have two message types linked to the same IDoc type. Each message type can now be referred in different logical systems without any clashes.
Now you can use BD64 to build your model using message types ORDERS and ORDERS2 without getting the multiple recepient error message.
Then use WE20 to set up each partner profile using your defined output conditions in message control to trigger the creation of the IDoc. Now you will beable to send the same Idoc type to different recepients.
source:http://sap.ittoolbox.com/groups/technical-functional/sap-interfaces/sap-distribution-model-3008763
Regards,
SuryaD.

Idoc Status error 29 for Out bound Idoc( Receiver of IDoc is its own logic)

I try to create the Out bound Idoc with messag type WMMBXY ( basic Idoc type - WMMBID02 ).
which is configured with the out put type XXXX in VT01N( shippment creation). But I am getting the error status 29 in the Idoc.
Only I am passing the sender, receiver port , partner type and partner function to the communication structure.
Could you please tell me , what is the issue with the partner type configuration .

Hi,
Error 29 occurs when there is an incomplete or no partner profile maintained.
Check whether you have done the correct partner profile settings in WE20 outbound parameters.
For the partner no defined in Idoc check whether there is an entry(under partner type LI, KU or LS)
with correct message type WMMBXY and Idoc type WMMBID02. Also check for message function code.
Regards,
Savitha

Issues with processing messages on one receive port causes problems on all the receive ports that are on the same handler

Greetings,
An integrator installed biztalk in our environment to process the hl7 message flow between their source application(s) and several receiving applications. We've had problems with this set-up for a while now because some receiving applications sometimes have
problems processing the messages. Be it either because there's problems with the server that processes the messages of a certain port or because there's problems with the software/daemon/service that needs to process these messages.
The main problem with this, is that the receiving end of this isn't under our control nor under control of the integrator, but when one receive port isn't processing their messages for a while it causes a problem with all the receive ports that are on the
same handler. So other receive ports start noticing a slow-down of their incoming messages until after a while nothing gets through anymore.
What is the best practice to prevent these kind of problems? Should we just create a handler for every receive port? Because that seems a bit overkill.
Thanks in advance.

What do you mean exactly with this question?
"Can you provide some more detail like BizTalk the receiver? "
The adapters are mainly file and MLLP, the MLLP adapters are already seperated from the file adapters (a handler for MLLP and a handler for file).
The problem with all the receive ports is that when one receive port isn't processing its messages (usually caused by the software processing the messages) the other receive ports on the same handler receive their messages/files a lot slower. If for any
reason the problem isn't fixed soon, the other receive ports on the same handler actually stop receiving any messages at all.
Isolating the receive port that causes the problems like la Cour suggested can work, but next time it might be another port that experiences this issue. So we are looking for a way to make sure the whole message flow isn't hindered by one port (whichever
port) that can't process its messages. Or rather by one receiving software that can't process its messages.

HL7 Unconsumed zombie ack messages suspended on MLLP R&R receive port from MLLP R&R send port.

      I have a content message routing scenario with request/response mllp receive and send port . Below are the points which describes the situation :-
      1) mllp message received from upstream application on receive port which sends back the direct synchronous ack .
      2) Message is routed to send port which sends the message to the downstream app and receive the ack from the downstream app.
      3) The ack received from downstream app is handled using a file type send port which dumps these acks to a folder.
      Now the issue which is occurring intermittently, is that the ack message received from the downstream application get suspended on the receive port with the below error -
      "The instance completed without consuming all of its messages. The instance and its unconsumed messages have been suspended." Error code - 0xC0C01B4C.
      This issue doesn't occur for all the messages. It seems the ack messages received by the send port, is searching the receive port instance which submitted the message to message box. But interestingly, not all the ack messages
are suspended.
      If anybody have any idea about this behavior , kindly respond..

I also need this question answering!
Comment from my host:
To prevent SPAM activity we have blocked the ability to send messages from our system where the FROM address is spoofed to anything other than the original sender's ID. The work around in your situation is to change the REPLY-TO address or switch to SMTP authentication.

Mass update of Outbound Receiver port in we20 - Customer

We want to change the Customer receiver port from a Transactional RFC to a File port. We have over 300 customers to change.
Can this be done in another way than manually updating one record at a time?
I tried using SCAT but could not get it to accept the Customer number as an input. I might have used it wrong, can scat be used to mass change the Customer port?
Any suggestions in this regard is appreciated.
liezel venter

The requested delivery date can be changed using Mass Maintenance (t/c MASS). The business object is BUS2032 for Sales Order but don't see any for Delivery mass update.
Alternatively
1) Extract all the document no's to be changed
2) Run LSMW and record a script, prepare the template
3) Fill in the template , create a flat file and run it in the system

Error Propagation on a 2 way receive port

Similar Messages

Maybe you are looking for