2011 Oct 07 5:15 PM
Hi experts,
I receiv DEBMAS IDocs from a external system.
We created for these customers a own account group with an own number range which can be changed externally.
The range is defined from 100000 to 200000 and the external system sends a customer with a customer number 2000 and also with the correct account group.
In my opinion an error should occur during idoc processing and the idoc should get an error status.
But the Idoc was booked without any information. And the customer has now a number outside the range.
What's wrong?
Is there any customizing to impact these?
If I create a customer manually it is not possible to use a number outside of the range!
Thanks for your help
Regards
Christian
2011 Oct 07 6:07 PM
The IDOC posts always with the number that is available in the IDOC itself.
That is a big advantage for all my migrations.
I know already the new number before the customer is created
And I dont have to switch number ranges from internal to external.
in general you can convert field values in this IMG path
Application Server > IDoc Interface / ALE >Modelling and Implementing Business Processes > Converting Data Between Sender and Receiver
With function module NUMBER_GET_NEXT you can retrieve a new number from the internal number range
Edited by: Jürgen L. on Oct 7, 2011 7:25 PM
Hi experts,
I receiv DEBMAS IDocs from a external system.
We created for these customers a own account group with an own number range which can be changed externally.
The range is defined from 100000 to 200000 and the external system sends a customer with a customer number 2000 and also with the correct account group.
In my opinion an error should occur during idoc processing and the idoc should get an error status.
But the Idoc was booked without any information. And the customer has now a number outside the range.
What's wrong?
Is there any customizing to impact these?
If I create a customer manually it is not possible to use a number outside of the range!
Thanks for your help
Regards
Christian
2011 Oct 07 6:07 PM
The IDOC posts always with the number that is available in the IDOC itself.
That is a big advantage for all my migrations.
I know already the new number before the customer is created
And I dont have to switch number ranges from internal to external.
in general you can convert field values in this IMG path
Application Server > IDoc Interface / ALE >Modelling and Implementing Business Processes > Converting Data Between Sender and Receiver
With function module NUMBER_GET_NEXT you can retrieve a new number from the internal number range
Edited by: Jürgen L. on Oct 7, 2011 7:25 PM
2011 Oct 08 1:03 PM
Hi Jürgen,
But I can not use the interal/automatic numbering of SAP because the leading system is the external system.
And I have do decide if I receive an update for an customer or a new customer.
This means If have to check (implement) manually during processing the IDoc if the sended number is inisde the range and if not I have to set an error status. Is tihs true?
If I understand well, this means also if I use internally numbering and I send a customer with a number inside the IDoc will be booked with the number from IDoc and not with the next number of the range? Is this true?
Just a qestion for the convertions rules:
How can I define this?
Can I only set constant values for the fields or are there other possiblities?
Regards
Christian
2011 Oct 08 4:20 PM
If I understand well, this means also if I use internally numbering and I send a customer with a number inside the IDoc will be booked with the number from IDoc and not with the next number of the range? Is this true?
yes this is true.
I have so far only used constant conversions
What is the reason for distrbution customers thru ALE and changing the customer number?
2011 Oct 08 4:49 PM
No I do not want to change the customer number.
How I already told, the external system is the leading system for the customer numbers.
The only thing what I want to have is a check, if the sent number from external system is outside the defined range of SAP, the IDoc (customer) should not be booked.
I know that this is a error of the external system because it should not sent wrong numbers but as far as I have seen it could happen.
So I think this check I have to implement...
2011 Oct 08 7:30 PM
You can filter the idocs, and only distribute those that have a number in the expected range
| User | Count |
|---|---|
| 3 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |