Hi Satish,
Two cents, do the screening of the BP using A1 and re-do the screening of the document using A2. If the system doesn't pick up the business partner with A1 screening, do the screening of the BP against the entire SPL using B1 and follow the document screening by B2. The version of 10.1 should allow you to release the document using A2 as suggested by Kul. Refer to KBA 1889911 which details about soft blocks.
Hope it helps!
-Shrini
Hello,
We are having a heavy sales order process and users would like to simplify the sample shipping somehow. There are insignificant quantities of them, so we had an idea to make a delivery without order and use an additional item category TAX or DLX (no stock, bo picking, no TO, no goods movement during PGI) for the materials that already exist and we sell them as TAN.
Then we can create a proforma and a commercial invoice but the thing is that proforma does not transfer to GTS. Is there any reason why we should not transfer TAX/DLX non stock items to GTS ? Can we customize it and what are the cons ?
Thank you very much.
Olaf
Hi Rahul,
You're not missing anything. That tab doesn't appear in the Pre-Declaration.
Why would you want calculation in a Pre-Declaration? Which country are you declaring in?
Regards,
Dave
Hi Olaf,
If you are talking about creating an Export Declaration, then it should work ok. Make sure that Foreign Trade data is being determined in the proforma, and check the configuration if not.
Regards,
Dave
Thanks for all your post.
Affective May 1st, EU Regulation around Long Term Vendor Declarations will change from yearly to 2-yearly.
Any ideas how SAP will deal with this?
When can we expect the oss notes to implement this change?
Thanks!
Hi,
We are getting SPL block for a quotation document when we change the business partner communication data (partner tab) in the document.
In SPRO we have only the name, city, street fields in the Address Comparison procedure and I assume communication data fields are not considered for screening.
So which fields does the system actually consider for changes during the screening document and blocking ?
How can we avoid a field from screening ?
Thanks
Sudesh
Hi Sudesh,
Which screening scenario are you using? Synchronous or asynchronous? and which version of GTS?
Regards,
Kul Vaibhav
Hi Kul,
That does help, thank you. I changed the address manually in sales order related delivery and it went on soft block too. It appears that soft block is caused by a combination of asynchronous and manual address change, can you confirm, please?
Thanks,
Satish
Hi Shrini,
Thanks for your response, Kul's explanation has the answer. Do you or Kul suggest changing it to synchronous? I think that makes more sense in my business.
Thanks,
Satish
Hi Satish,
Yes, your understanding is correct. If you have configured asynchronous screening scenario and address is changed manually, system will park the document with soft block and will wait for your action to run A2 scenario manually or through batch job.
If system was configured for synchronous screening, it would have given result immediately.
regards,
Kul Vaibhav
Hi Satish,
it really depends upon business process and requirement. Generally if volume of business partner creation/change is huge, it makes sense to use asynchronous screening and screen them periodically via batch job, for performance reasons. In other cases, synchronous is generally preferred as it gives immediate results.
regards,
Kul Vaibhav
Hi Wardell,
I will try to answer some of your queries if not all. I will try to keep it simple however before I go to your specific queries, let me brief you about some basics which will help you to understand better.
Application buffer is basically used to enhance the system performance by storing some frequently used data in buffer or internal memory which allows a program to response faster by not requiring to query database every time, instead it takes the needed information from this internal memory called application buffer which helps to boost system performance.
GTS doesn't compares the address directly but it compares it's search terms or comparison terms. As a prerequisite it is important that all the address elements like name, street, city, country etc. are broken down into small search terms or comparison terms which can be used in address comparison later. Search term is created for both business partner address and SPL address.
An index is nothing but a collection or combination of all these search terms after aggregation.
Now coming to your specific questions:
1) as explained above. I don't think we can see application buffer data but someone can correct me here. Resetting application buffer ensures that all the old data has been removed and fresh data can be written over it so that new settings can take effect.
2) as explained above, every address element will be broken down into small search terms as per system settings. We can see the search terms in following tables:
a) for SPL name - /SAPSLL/TSPLNK
b) for SPL address - /SAPSLL/TSPLAK
3) as explained above. In this step, system stores the comparison/search terms in application buffer and/or cluster tables depending upon customizing settings. You can see the index in table /SAPSLL/APPIDX
4) as explained above, searh term is created for both SPL address and business partner address. This transaction is used to create search terms for business partner address which helps to boost system performance. We can see search terms for business partner in table - /SAPSLL/ADRCMP
5) After we have received a delta file form data provider, it is important to screen all the existing business partners against this delta list. This will ensure that your system remains complaint and updated with recent changes in denied party list. This program is used to screen business partners against delta SPL.
All these steps should be executed after we receive a delta file from third party content provider or if some changes are made in SPL customizing.
I hope above explanation helps and gives you some more insight on this topic.
Regard,
Kul Vaibhav
Hi Dave
Can you explain where / how values need to maintain, as we are getting error at message incompletion "Ult. Consignee Type must have a value other than O"
Point 2: " If there's an Ultimate Consignee partner, it checks that the type is D, G, O or R. Those GTS values map to message values XT, QW, B2 and DU.
Though it is old post but not able to find any other related solution..
Regards- AK
Hi Shakti,
Please make sure that your legal regulation is active as per determination procedure assigned to service "legal control". Once it is in place, it should be visible in this drop down.
Regards,
Kul Vaibhav
Dear experts,
before create the customs declaration, we want to verify the information between the B/L and inbound delivery .
How the create the B/L in GTS?
Which method we can use?only manually or other method.
now the forwarder only give the pdf file to us.
thanks.
Hi Amit,
Please check following, you should be good:
1) Legal Regulation ACE is activated as per determination procedure assigned for Customs Processing.
2) A Numbering Scheme is assigned to legal regulation ACE for Commodity Codes.
regards,
Kul Vaibhav
Hi Tiwari,
1) For each document in feeder system like Sales Order or Delivey, a corresponding mirror document is created in GTS called customs document. Legal regulation in this document is determined automatically. It is not transferred from feeder system. Legal Regulation helps to determine which services are active for this business transaction. Determination Procedure is requied to allow system to do this determination automatically based on settings defined under determination procedure.
2) Determination strategy is one of main the elements under determination procedure which can be viewed as access sequence. Here you can configure the sequence in which system should search for active legal regulation. There are six options to chose from which you can find in the drop down.
Regard,
Kul Vaibhav
Hello Thomas,
Thanks for you inputs.
Regards
Hi ,
can you please tell me List of BAPI/FM to update product master data in GTS system.