Это видео недоступно.
Сожалеем об этом.

SAP IDOC Outbound and Inbound

Поделиться
HTML-код
  • Опубликовано: 18 авг 2024
  • SAP Outbound and Inbound IDOC for PO and Inbound Delivery

Комментарии • 20

  • @rakeshmr64
    @rakeshmr64 3 месяца назад

    Mind-blowing video this is what we required for functional consultants, keep uploading such videos sir,
    Like : FS writing in WM module with real time scenario. And RF transactions ,
    User exit in real time experience in WM module

  • @vivekp8269
    @vivekp8269 Год назад

    Thanks for sharing the knowledge.. explained very well 👏 👌

  • @draco1847
    @draco1847 5 месяцев назад

    Incredible video

  • @yellappajaviniki8067
    @yellappajaviniki8067 6 месяцев назад

    Very nice explanation

  • @rameshb7683
    @rameshb7683 2 года назад

    very nice explanation, Thanks

  • @mandalaneniram4952
    @mandalaneniram4952 2 года назад

    Very useful session thanks

  • @SrinivasSrinivas-ms8oi
    @SrinivasSrinivas-ms8oi Год назад

    nice details mentioned in video, but I need how to create Inbound and outbound IDOC

  • @mmadhuroyal
    @mmadhuroyal 5 месяцев назад

    thank you sir

  • @rowdyboy411
    @rowdyboy411 2 года назад

    Can you please explain how to delete child segments from parent segments through program

  • @mintukumarigupta4549
    @mintukumarigupta4549 2 года назад

    Thanks

  • @xerogiga
    @xerogiga 2 года назад

    nice details mentioned in video, although I still have a question in my mind.. so the way these inbound happened is through output type of a process ( PO process in the example), which is like automatically run without triggering it manually (except for testing purpose) .. so, is it the best way for standard tcode (ME21N, VA01, MIGO, etc) with output type idoc to also use the standard message type and basic type instead of creating a custom message type or custom basic type?

    • @irus2000
      @irus2000  2 года назад +1

      Hi Siswanto, you can use custom message type or custom basic type if you have enhanced your standard tcode (ME21N, VA01). suppose you have enhanced your PO header with additional tab now to send this additional information by IDOC you need to either enhance the Basic type or create a new basic type because standard IDOC basic type doesn't have segment to send this information. In the partner profile you can configure your custom message type and custom basic type. Such scenarios will involve new GAP and ABAP work.

    • @xerogiga
      @xerogiga 2 года назад

      @@irus2000 i see, so as long as there is a standard segment which could send the field i wanted then the segment could be used, else, a new custom segment type and message type would be needed.
      Noted. Many thanks

  • @ravishankartiwary8561
    @ravishankartiwary8561 Год назад

    do you provide any online course ? very good explanation

    • @irus2000
      @irus2000  Год назад

      No Ravi, just make tutorials for SAP aspirants

  • @ajayjadhav-rn2vv
    @ajayjadhav-rn2vv 2 года назад

    Only this comes under the IDOC process. Or also different transaction are there ?

    • @irus2000
      @irus2000  2 года назад

      Hi Ajay, IDoc related transactions are WE** . You can check one master transaction WEDI, it covers all IDoc transaction mostly

    • @irus2000
      @irus2000  2 года назад

      Through the process code go to function module and in this FM find suitable call customer which is a customer exit. Loop the edidd table and as soon as you get you segment name delete it.

  • @gramesh8874
    @gramesh8874 10 месяцев назад

    sir, interviews idocs questions asking on on edi,ale or api in s4 hana?

    • @irus2000
      @irus2000  9 месяцев назад

      Hi Ramesh, please wtach end part of this viedo ruclips.net/video/gYCA3gczYrE/видео.html