cancel
Showing results for 
Search instead for 
Did you mean: 

Update rule failed to transport

Former Member
0 Kudos

Hi,

I'm facing an error while transporting 0BPartner infoobject's update rule to production.  This update rule is inactive in Production.  Hence I've activated the update rule and locked with a request and moved it.  But the following is the error I'm getting.  Please suggest solution to solve the issue.

Start of the after-import method RS_IOBJ_AFTER_IMPORT for object type(s) IOBJ (Activation Mode)

Value "mascotapforesite@yahoo.co.in#" (HEX 006D006100730063006F0074006100700066006F0072006500) of characteristic 0EMAIL_AD contains

Value "dhulevision@hotmail.com#" (HEX 006400680075006C00650076006900730069006F006E004000) of characteristic 0EMAIL_ADDR contains an

Error when activating InfoObject 0BPARTNER

Characteristic 0BPARTNER: Error when generating master data routines

Error when resetting InfoObject 0BPARTNER to the active version

Start of the after-import method RS_UPDR_AFTER_IMPORT for object type(s) UPDR (Activation Mode)

InfoProvider 0BPARTNER set to 'INACTIVE'

Error RSAU 255 during after import handling of objects with type(s) UPDR

Errors occurred during post-handling RS_AFTER_IMPORT for IOBJ L

The errors affect the following components:

    BW-WHM (Warehouse Management)

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hi Jerald,

Can you check if there is any difference in the field "Content release" in the General tab of the Infoobject between development & production?

Also check if all the attributes available in Development are there in Production

Prathish

Former Member
0 Kudos

Hi,

     I could find a difference in "content release" while comparing bet dev and production.  In dev, in content release it's 7.0/04 and in production, it's 3.5/03.  Also all the attributes available in development are there in production.

So since there's a difference, is this affects transporting requests?  Please suggest solution..

with Regards,

Antony Jerald

Former Member
0 Kudos

You need to go fix the data in master data table in se16 by debugging.

I had the same problem and this is the only quick fix unless you want to delete the data and retransport everything.

Just find the value in the table and edit it remove the # symbol.

Cheers!