Dear ​@MadFerIt 

Honestly am missing several information to provide a fit response, but sharing some understanding based on the generic question “how to block an authorizer”  Note: Screenshots are from cloud version as app 10 is not accessible

1. To stop an authorizer from authorizing , you may BLOCK the respective authorizer in the Purchase Order Authorization Basic data screen . See screen shot 1, use the menu options to toggle any authorizer as Active or BLOCKED.
2. If the authorization routing rule is to be changed, this can also be done in the same screen, to remove from listing the authorizer within a PO as an authorizer. See screenshot  2.  Replace with a different person or remove the individual altogether. A new routing template can also be defined and updated in the PO authorization rules.

If you are trying something else beyond this, that is not clear from the above question. Please explain

Screenshot 1 

Screenshot 2 

Hello, thank you for the reply. I know the manual process. Im interested in the automatic process by API (odata).

Im referring to the API explorer:

Hi ​@MadFerIt 

There are options for SetHidden and SetBlocked.  Not sure if the below helps. I found them under  PurchaseAuthorizationBasicDataHandling in the API Explorer.  

"/PurchaseAuthorizerSet(Company='{Company}',AuthorizeId='{AuthorizeId}')/IfsApp.PurchaseAuthorizationBasicDataHandling.PurchaseAuthorizer_SetHidden":{"post":{"tags"::"PurchaseAuthorizerSet"],"summary":"Invoke action SetHidden","description":"Invoke action SetHidden","operationId":"PurchaseAuthorizationBasicDataHandling.PurchaseAuthorizerSet.PurchaseAuthorizer.SetHidden","parameters":a{"name":"If-Match","in":"header","description":"E-Tag","required":true,"type":"string","uniqueItems":true},{"name":"Company","in":"path","description":"key: Company","required":true,"type":"string"},{"name":"AuthorizeId","in":"path","description":"key: AuthorizeId","required":true,"type":"string"}],"responses":{"204":{"description":"No Content"},"400":{"$ref":"#/responses/400"},"403":{"$ref":"#/responses/403"},"404":{"$ref":"#/responses/404"},"405":{"$ref":"#/responses/405"},"500":{"$ref":"#/responses/500"},"501":{"$ref":"#/responses/501"},"503":{"$ref":"#/responses/503"},"504":{"$ref":"#/responses/504"}}}},"/PurchaseAuthorizerSet(Company='{Company}',AuthorizeId='{AuthorizeId}')/IfsApp.PurchaseAuthorizationBasicDataHandling.PurchaseAuthorizer_SetBlocked":{"post":{"tags"::"PurchaseAuthorizerSet"],"summary":"Invoke action SetBlocked","description":"Invoke action SetBlocked","operationId":"PurchaseAuthorizationBasicDataHandling.PurchaseAuthorizerSet.PurchaseAuthorizer.SetBlocked","parameters":a{"name":"If-Match","in":"header","description":"E-Tag","required":true,"type":"string","uniqueItems":true},{"name":"Company","in":"path","description":"key: Company","required":true,"type":"string"},{"name":"AuthorizeId","in":"path","description":"key: AuthorizeId","required":true,"type":"string"}],

Yes, “

/PurchaseAuthorizerSet(Company='{Company}',AuthorizeId='{AuthorizeId}')/IfsApp.PurchaseAuthorizationBasicDataHandling.PurchaseAuthorizer_SetHidden"

is the url im looking for.. Its the “same” logic as the function for PurchBuyers but there the endpoint is visible from the menu. Thx for the the help

No luck on our version. Seems to be missing on this endpoint