on 11-05-2012 2:01 AM
PSM Request - Allow Write for Address Node in Supplier BO
I need write access to the Supplier BO at the Address node.
Use Case: Mass update of State and Tax Jurisdictions that were migrated incorrectly
BO Effected: Supplier
Node Effected: Address
I am requewsting that all nodes and fields below the Supplier Address node have read/write access.
There is no impact to any UI
Anyone willing to wager on how long this will take?
Hi Judson,
after reading your post, I have a question. The many possibilities of Uploading Mass Data (Customer/Supplier Data) irritate me. I want to upload Supplier/Customer Data into the Customer Test Tenant and schedule jobs for the data runs in the "Application and User Management" Work Center. It is also possible to use the work-center "Business Partner Data" to upload new customers and suppliers into ByD (via Excel-AddIn) which is interactive. But the customer wants to make Data Runs and therefore we need Service Interfaces for scheduling jobs and update master data.
I also have a Development Tenant where I can choose the created Service Integration Interfaces I´ve created with ByD Studio. But so far I don´t know what to do If I want to make Data Runs for Suppliers/Customers and schedule a job. I am not able to create a XML-Structure for the Customer or Supplier Business Object in ByD Studio by using the Service Integration Wizard for the XML-file input. How does it exactly work?I can only choose the given business objects in the service integration wizard (e.g. supplier invoice, customer invoice) but not the master data business objects like customer, supplier...You use the Scripting language to update your supplier data. Can you or someone make a tutorial/describe how it exactly works? Because I don´t find a proper documentation about this case. Only about implementing a new business object or extend the existing business objects with new fields (Epic Tutorial was great btw ! ).
Cheers
Rufat Gadirov
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hey There,
My 'Epic Tutorial' already has what you're looking for. It comes down to these steps:
1) Create custom BO containing the Supplier/Customer ID, and target fields you want to update.
2) Create an XML File Upload Service Integration on the custom BO
3) Write an ABSL script where you query the target BO, where the target BO Customer/Supplier ID = your Custom BO supplier ID.
4) Write a foreach loop that specifies that for each result above, execute X command (Set State = "CA", whatever)
3) Load the custom BO via the File Input UI and run the Service Integration and run it
4) Done.
Hello Judson,
thank you very much for your quick answer. I have some questions left:
1) Which type of solution do you use for developing Service Integration Interfaces for Data Runs? In your current post you use a customer specific solution. But it´s not possible to create XML-File Input via the Service Integration Wizard by choosing this kind of solution type. The sdk tells me, that the "entity type pid is not supported in Reseller Mode". Thefore I use the solution Type "AddOn". Do I have to request a quality review and so on, just because I want to develop a Service Interface for a customer? How do I import the AddOn into the customers test tenant, because it is not possible to log in into the customers test tenant with the sdk. By developing a customer speicifc solution one can use the implementation manager for uploading the solution. Therefore it´s not really clear for me.
2) The ABSL-Script ->You mean the AfterModify - Event?
Cheers,
Rufat Gadirov
1) You must use a 4.0 tenant for this to work in reseller mode
2) Follow the instructions and documentation on deploying customer solutions
3) If you need some more help you can email me at jewickhm@gmail.com
okay, this is ridiculous.
The AddressInformation node is PSM write enabled, but only via its association "CurrentDefaultAddressInformation". And since, as soon as an instance of Supplier or any BusinessPartner is created, this association is also created by default, so you cannot create a new instance later. Same goes for the underlying node "Address" whose elements actually contain the various address fields. A default instance of node "Address" is created and can only be edited via future code.
Judson, if your use case is only about updating the existing data, it can be done.
Need to check the same on how the ManageSupplierIn webservice works.
Regards
Asif
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Dude, it's in the freaking post:
I need write access to the Supplier BO at the Address node.
Use Case: Mass update of State and Tax Jurisdictions that were migrated incorrectly
BO Effected: Supplier
Node Effected: Address
I am requesting that all nodes and fields below the Supplier Address node have read/write access.
There is no impact to any UI
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Judson,
the PSM documentation is valid and write-access to address attributes of a supplier also works in FP4.0. I do not know what you have tried exactly.
Therefore here a working example (which I ran in our internal system) with write-access to the region code within the address of a supplier:
import ABSL;
import AP.FO.BusinessPartner.Global;
var supplier_instance;
supplier_instance = Supplier.Create();
supplier_instance.AddressInformation.Address.DefaultPostalAddressRepresentation.GetFirst().RegionCode.content = "NV";
I hope this helps.
Regards,
Thomas
HI Judson,
I just checked. I was able to update the current default address information without any issues.
I created a test BO with one attribute called Supplier ID. I would populate that attribute from a custom UI and was able to do this.
import ABSL;
import AP.FO.BusinessPartner.Global;
var supplier = Supplier.Retrieve(this.SupplierID);
if(supplier.IsSet())
{
var address = supplier.CurrentDefaultAddressInformation.Address;
address.DefaultPostalAddressRepresentation.CityName = "Bangalore";
address.DefaultPostalAddressRepresentation.HouseID = "123";
}
However, I could not add a completely new address. Let me test that.
Regards
Asif
Hi Judson,
as SAP employee I of course can switch of PSM restrictions but nevertheless did my test with PSM active.
Since you are working in a customer test tenant environment I assume you are still restricted to pure read-only access within PSM. Please check the following business center document to remove this
restriction for your tenant: https://wiki.sme.sap.com/wiki/display/AMI/What+to+know+about+development+of+customer+specific+soluti...
Simply open an incident from your test tenant and we will remove the PSM restriction. Unfortunately, this process is still necessary to control write-access on customer tenants for security reasons.
Regards,
Thomas
Judson,
Did you try raising this request from your partner coach. That would help you to follow it up as well.
The point is even if you raise, SAP will have its own checks to perform to get it released. Sometimes, they might come with the answer "Can't release".
In the worst case, it took more than 2 weeks for me to get a field released in some Financial related standard BO.
I think, there should be no serious problem on your particular PSM request. Sounds generic. Good luck.
Lets wait for Rainer to publish the list. Hoping for a huge delta list. (am I exaggerating? )
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Judson,
I am currently traveling, but will publish the standard SLA for PSM entries as soon as I am back on ground.
Best regards
Rainre Zinow
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
89 | |
7 | |
6 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 | |
2 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.